WO2021022919A1 - 对用户设备进行接入控制的方法，网络系统及相关设备 - Google Patents

对用户设备进行接入控制的方法，网络系统及相关设备 Download PDF

Info

Publication number
WO2021022919A1
WO2021022919A1 PCT/CN2020/097542 CN2020097542W WO2021022919A1 WO 2021022919 A1 WO2021022919 A1 WO 2021022919A1 CN 2020097542 W CN2020097542 W CN 2020097542W WO 2021022919 A1 WO2021022919 A1 WO 2021022919A1
Authority
WO
WIPO (PCT)
Prior art keywords
user equipment
management device
access node
mobility management
access
Prior art date
Application number
PCT/CN2020/097542
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 华为技术有限公司
Priority to EP20850785.5A priority Critical patent/EP3972376A4/en
Publication of WO2021022919A1 publication Critical patent/WO2021022919A1/zh
Priority to US17/586,140 priority patent/US20220150797A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/24—Accounting or billing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/02—Access restriction performed under specific conditions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1403—Architecture for metering, charging or billing
    • H04L12/1407—Policy-and-charging control [PCC] architecture
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/66—Policy and charging system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/80—Rating or billing plans; Tariff determination aspects
    • H04M15/8016—Rating or billing plans; Tariff determination aspects based on quality of service [QoS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/82—Criteria or parameters used for performing billing operations
    • H04M15/8228—Session based
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/08—Testing, supervising or monitoring using real traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
    • H04W8/24—Transfer of terminal data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H04W60/04—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration using triggered events
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H04W8/20—Transfer of user or subscriber data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/18—Service support devices; Network management devices

Definitions

  • the present invention relates to the field of communication technology, in particular to a method for access control of user equipment, a network system and related equipment.
  • the mobile communication network supports the non-independent networking architecture; in the non-independent networking architecture, the user equipment can establish a connection with two access nodes at the same time; the service data of the user equipment can pass through either or both of the two access nodes. Forwarded. In the non-independent networking architecture, the user equipment may also only establish a connection with one access node.
  • the user equipment establishes a connection with two access nodes.
  • the user equipment can be called a dual-connection user equipment.
  • the connection type of the user equipment is dual-connection; the user equipment only establishes a connection with one access node, and the user equipment can be called a single Connect the user equipment, the connection type of the user equipment is single connection.
  • the technical problem to be solved by the embodiments of the present invention is to provide a method for access control of user equipment, a network system and related products, which are used to identify the connection type of the user equipment and provide support for targeted services.
  • an embodiment of the present invention provides a method for performing access control on user equipment, the method including:
  • the mobility management device identifies the connection type used by the user equipment to access the core network through the access node device, and the connection type is single connection or dual connection; when the connection type is single connection, the user equipment passes through one An access node device accesses the core network; in a case where the connection type is dual connectivity, the user equipment accesses the core network through two access node devices;
  • the mobility management device performs access control on the user equipment according to the connection type of the user equipment.
  • the access node device can be called an access node, for example, in a fourth-generation (4G) network or a fifth-generation (5G) network
  • the base station the same user equipment can access two base stations, such as the primary access node and the secondary access node.
  • the mobility management device may be a mobility management entity (MME) or an access and mobility management function (access and mobility management function, AMF) device.
  • MME mobility management entity
  • AMF access and mobility management function
  • the mobile management device performs access control on the user equipment.
  • the connection type the mobile management device determines that the user equipment has dual-connection capability or subscribes for dual-connection. If the user equipment currently uses single-connection, it will It performs access control so that the user equipment cannot use service data; or, it performs different permission control on single-connection user equipment or multi-connection user equipment.
  • the specific process is not uniquely limited in the embodiment of the present invention.
  • this embodiment uses the mobile management device to identify the connection type of the user equipment, and the identification function can be aggregated in a fixed device;
  • the mobility management device is the core network device that the user equipment first accesses via the access node device. Therefore, if the mobility management device performs targeted services such as access control, it is more important to notify the mobility management device after being identified by other devices. In order to be timely, the delay is smaller.
  • connection type used by the mobility management device to identify that the user equipment accesses the core network through the access node device includes:
  • the mobility management device determines the connection type of the user equipment according to one or more of the dual connection capability of the user equipment, the subscription information of the user equipment, and the local configuration of the mobility management device;
  • the mobility management device receives a data usage report sent by the access node device, where the data usage report contains traffic information of the user equipment, and the mobility management device determines the user equipment according to the data usage report Connection type;
  • the mobility management device receives a message carrying the internet protocol (IP) address of the access node device, and the mobility management device determines the connection of the user equipment according to the IP address of the access node device Types of.
  • IP internet protocol
  • the mobile management device determines the connection type of the user equipment.
  • the access node device sends the access type parameter to the mobile management device through a message, and the mobile management device determines the connection type of the user equipment according to the access type parameter.
  • the message carrying the access type parameter may be the message used in the process of establishing, updating, and deleting the bearer related to the above-mentioned user equipment, such as: a radio access bearer update request message, etc., or a dedicated
  • the message to carry the access type parameter which is not uniquely limited in this embodiment.
  • the specific means for the access type parameter to indicate the wireless access type of the user equipment or the type of the access node device may be a direct indication, or it may be a parameter that can be identified by the mobility management device. The embodiments of the invention are not uniquely limited.
  • the mobile management device can directly obtain the connection type of the user equipment from the carried information, which is more efficient.
  • the mobile management device obtains the parameters required to determine the connection type, and then determines the connection type of the user equipment accordingly.
  • the dual connectivity capability of the user equipment can be reported by the user equipment during network registration;
  • the user's subscription information can also carry information about whether the user equipment is allowed to use dual connectivity, and the mobility management device can be from the device that stores the subscription information, such as home Obtained from the user server;
  • the local configuration of the mobile management device can also include information about whether the user equipment is allowed to use dual connectivity;
  • the mobile management device can be based on one of the dual connectivity capabilities of the user equipment, the user’s subscription information, and the local configuration or Multiple items determine the connection type.
  • the mobility management device can indirectly obtain a more accurate connection type of the user equipment compared to the foregoing first method, which can further reduce the use of signaling and the transmission of data.
  • the third method is mainly determined by the impact of single connection or dual connection on the data usage report; the fourth method is to distinguish the types of different access node devices by IP address, such as the first base station or the second base station.
  • One base station may be a 4G base station, the second base station may be a 5G base station, or both the first base station and the second base station may be 5G base stations; based on this, the connection type of the user equipment is determined.
  • the first base station and the second base station of the dual-connected user equipment are 4G base stations and 5G base stations respectively.
  • the dual-connected Both the first base station and the second base station that the user equipment accesses are 5G base stations.
  • the third method provides a means for intelligently identifying the connection type of the user equipment by the mobile management device, and does not need to rely on existing or transmitted data for identifying the connection type of the user equipment.
  • the primary access node (or the first access node, the primary access node device), the eNodeB, and the 4G base station are collectively referred to as the first base station;
  • the secondary access node (or the second access node) , Secondary access node equipment), next generation NodeB (gNB), evolved NodeB (eNB), and 5G base station are collectively referred to as the second base station.
  • gNB next generation NodeB
  • eNB evolved NodeB
  • 5G base station 5G base station
  • the mobility management device receives the access type parameter of the user equipment sent by the access node device; the mobility management device determines the connection type of the user equipment according to the access type parameter , Specifically including:
  • the mobility management device receives a radio access bearer update request message, or a channel switching request message, or a service flow notification message sent by an access node device; in the radio access bearer update request message, or the channel switching request
  • the message or the notification message of the service flow includes the access type parameter; the mobility management device determines the connection type of the user equipment according to the access type parameter.
  • This embodiment provides several examples of specific messages that may be used to carry access type parameters. Using the messages in the above examples to carry access type parameters eliminates the need for new signaling, and has better compatibility with existing processes.
  • the mobility management device receives a message carrying the Internet Protocol IP address of the access node device, and the mobility management device determines the user equipment's IP address according to the IP address of the access node device.
  • Connection types include:
  • the mobility management device receives an initial context establishment response message, a packet data unit (packet data unit, PDU) session resource establishment response message or a default bearer establishment response message, in the initial context establishment response message, a PDU session resource establishment response message, or
  • the default bearer establishment response message carries the IP address of the access node device, and the mobility management device determines the connection type of the user equipment according to the IP address of the access node device.
  • This embodiment provides several examples of specific messages that the access node device sends the access type parameters to the mobility management device. It can be understood that carrying them in other messages or sending them using dedicated messages will not affect the performance of the embodiments of the present invention. achieve. Using the above messages, there is no need to add new message types, and the access type parameters or changes in the access type parameters can be reported in time, so that the mobile management device can accurately and timely determine the connection type of the user equipment.
  • the mobility management device determines the user according to one or more of the dual connectivity capability of the user equipment, the subscription information of the user equipment, and the local configuration of the mobility management device
  • the connection types of the device include:
  • the mobility management device receives the information about the dual connection capability of the user equipment sent by the user equipment; the mobility management device determines the connection type of the user equipment according to the information about the dual connection capability of the user equipment, or ,
  • the mobility management device obtains the subscription information of the user equipment from the home user server of the user equipment, and determines the connection type of the user equipment according to the subscription information, or,
  • the mobility management device acquires the local configuration of the mobility management device, and the local configuration includes information about whether to allow the user equipment to establish dual connections; and determines the connection type of the user equipment according to the local configuration.
  • the connection type of the user equipment is dual connection, otherwise it is single connection; if the subscription information contains information that the user equipment has dual connection capability, it can be determined that The connection type of the user equipment is dual connection, otherwise it is single connection; if the above local configuration allows the user equipment to use dual connection, the connection type of the user equipment is determined to be dual connection, otherwise it is single connection; the above three factors can also be combined, If all is yes, it is determined as dual connection, otherwise it is single connection, or if one of them is yes, then it is determined as dual connection, otherwise it is single connection, or if all is yes, then it is determined as dual connection, if all is yes, it is determined as single connection, other cases It is determined that the connection type cannot be determined.
  • the mobility management device receives the data usage report sent by the access node device, the data usage report contains traffic information of the user equipment, and the mobility management device uses the data according to the data usage report.
  • the report determines that the connection type of the user equipment includes:
  • the mobility management device determines that the data usage report sent by the access node device is received within the connected state period of the user equipment, and then determines that the connection type of the user equipment is dual connection.
  • the mobility management device determines that the data usage report sent by the access node device is not received within the connected state period of the user equipment, then it is determined that the connection type of the user equipment is single connection.
  • connection type of the user equipment is determined by whether the data usage report sent by the access node device is received during the connected state period, and it is unnecessary to consume additional signaling to determine the connection type of the user equipment.
  • the mobility management device determining the connection type of the user equipment according to the received IP address of the access node device includes:
  • the mobility management device distinguishes the access node device into the first base station or the second base station according to the received IP address of the access node device;
  • the mobility management device determines that the connection type of the user equipment is dual connectivity
  • the mobility management device determines that the connection type of the user equipment is single connection.
  • the mobility management device can determine whether the type of the access node device is the first base station or the second base station according to the IP address, and then determine the connection type according to which type of access node device the user equipment is connected to .
  • the IP address can be reported to the mobility management device according to an existing process, so no additional signaling is required, which saves signaling overhead.
  • the mobility management device distinguishes the access node device into the first base station or the second base station according to the received IP address of the access node device, including:
  • the mobility management device after receiving the IP address of the access node device, assigns the access node device to the IP address of the access node device Mark as the first base station;
  • the mobility management device receives the IP address of the access node device in the process of establishing the forwarding channel of the service data packet to the first base station, and marks the access node device corresponding to the IP address of the access node device as the first base station ;
  • the mobility management device When the user equipment accesses two IP addresses, and the access node device corresponding to one of the IP addresses is the first base station, the mobility management device connects the other of the two IP addresses to the corresponding one.
  • the ingress device is marked as the second base station.
  • the type of base station to which the access node belongs is marked by analyzing the received IP address, and different types of base stations can be accurately identified.
  • the process of establishing the forwarding channel of the service data packet to the first base station includes:
  • Any one of the registration process, tracking area update, service request process, and attachment process is any one of the registration process, tracking area update, service request process, and attachment process.
  • This embodiment provides a specific implementation method of how to mark the type of access node equipment. Among them, it is used when the user equipment is not allowed to establish dual connections, which may be the local configuration of the mobile management device.
  • the above user equipment does not have the dual connection capability, or the situation where it cannot establish dual connections for other reasons; due to the specific process, such as Tracking area update, service request process and attachment process, etc.
  • the main access node usually first establishes the forwarding channel of the carried service data packet to the main access node, that is, sends to the IP address and tunnel of the access node of the mobility management device
  • the endpoint identifier (tunnel endpoint identifier, TEID) is usually assigned to the main access node, so it can be marked as the first base station; in the scenario of dual connectivity, there is usually one first base station and the other second base station. In the case where one is the first base station, the other is the second base station.
  • This embodiment can accurately mark different types of base stations without increasing network overhead, and provide a basis for identifying the connection type of the user equipment.
  • the method further includes:
  • the mobility management device deletes the information that the access node device corresponding to the marked IP address is the first base station or the second base station after a predetermined time after marking the access node device corresponding to the IP address as the first base station or the second base station .
  • the set predetermined time is the aging time
  • the aging timer can be used to realize timing. After a certain IP address is marked, the timer expires and the mark of the IP address is deleted, which can ensure the accuracy of marking .
  • the method further includes:
  • the mobility management device sends the identified connection type to the gateway device.
  • the gateway device may include a serving gateway (serving gateway, SGW) in a 4G network, a data gateway (PDN gateway, PGW), a session management function (SMF) device in a 5G network, and a user plane Function (user plane function, UPF) equipment, etc.
  • serving gateway serving gateway
  • PGW data gateway
  • SMF session management function
  • UPF user plane Function
  • connection type identification method including:
  • the access node device determines the access type parameter of the user equipment, and sends the access type parameter of the user equipment to the mobility management device, where the access type parameter is used to indicate the wireless access type of the user equipment or the access node Type of equipment;
  • the mobility management device receives the access type parameter of the user equipment sent by the access node device, and determines the connection type of the user equipment according to the access type parameter.
  • the sending the access type parameter of the user equipment to the mobility management device includes:
  • the access node device sends a radio access bearer update request message, or a channel switch request message, or a service flow notification message to the mobility management device; in the radio access bearer update request message, or the channel switch
  • the request message or the notification message of the service flow includes the access type parameter.
  • an embodiment of the present invention also provides a network system, including: a mobile management device and a gateway device;
  • the mobility management device is used to execute any method process provided by the embodiment of the present invention.
  • the gateway device is configured to perform service quality control or charging control on the user equipment according to the connection type.
  • the network system further includes a policy control function device, a session management device or a user plane function device;
  • the mobility management device is further configured to send the connection type to the policy control function device, the session management device, or the user plane function device;
  • the policy control function device is configured to issue a quality of service policy or a charging control policy to the user equipment according to the connection type; or,
  • the session management device is configured to perform service quality control or charging control on the user equipment according to the connection type; or,
  • the user plane function device is configured to perform service quality control or charging control on the user equipment according to the connection type.
  • an embodiment of the present invention also provides a mobility management device, including:
  • the identification unit is used to identify the connection type used by the user equipment to access the core network through the access node device, where the connection type is single connection or dual connection; when the connection type is single connection, the user equipment Access to the core network through one access node device; in a case where the connection type is dual connectivity, the user equipment accesses the core network through two access node devices;
  • the access control unit is configured to perform access control on the user equipment according to the connection type of the user equipment.
  • the identification unit is configured to determine the connection type of the user equipment according to the access type parameter of the user equipment sent by the access node device, and the access type parameter is used to indicate The wireless access type of the user equipment or the type of the access node device;
  • receiving a data usage report sent by the access node device where the data usage report contains traffic information of the user equipment, and the mobility management device determines the connection type of the user equipment according to the data usage report;
  • receiving a message carrying the Internet Protocol IP address of the access node device and determining the connection type of the user equipment according to the IP address of the access node device.
  • the identification unit is configured to determine the connection type of the user equipment according to the access type parameter of the user equipment sent by the access node device, including: The access bearer update request message, or the channel switching request message, or the access type parameter included in the notification message of the service flow determines the connection type of the user equipment.
  • the identification unit is configured to receive a message carrying the Internet Protocol IP address of the access node device, and determining the connection type of the user equipment according to the IP address of the access node device includes :
  • the identification unit is configured to determine the user equipment based on one or more of the dual connectivity capability of the user equipment, the subscription information of the user equipment, and the local configuration of the mobility management device.
  • the connection types of the user equipment include:
  • the identification unit is configured to receive a data usage report sent by the access node device, the data usage report contains traffic information of the user equipment, and the mobility management device Using the report to determine the connection type of the user equipment includes: determining that the data usage report sent by the access node device is received during the connected state period of the user equipment, and then determining that the connection type of the user equipment is dual connection . On the other hand, if it is determined that the data usage report sent by the access node device is not received within the connected state period of the user equipment, then it is determined that the connection type of the user equipment is single connection.
  • the mobility management device further includes:
  • the marking unit is used to distinguish the access node device as the first base station or the second base station according to the received IP address of the access node device;
  • the identification unit is specifically configured to determine that the connection type of the user equipment is dual connection when the access node equipment accessed by the user equipment includes a first base station and a second base station; When the access node device accessed by the user equipment includes only the first base station, the mobility management device determines that the connection type of the user equipment is single connection.
  • the marking unit is configured to, when the user equipment is not allowed to establish dual connections, the mobility management device, after receiving the IP address of the access node device, set The access node device corresponding to the IP address of the access node device is marked as the first base station; the IP address of the access node device received in the process of acquiring the forwarding channel of the service data packet and establishing the first base station is used to transfer the access node device The access node device corresponding to the IP address of the ingress node device is marked as the first base station; when the user equipment accesses two IP addresses, and the access node device corresponding to one of the IP addresses is the first base station, the The access node device corresponding to the other of the two IP addresses is marked as the second base station.
  • the process of establishing the forwarding channel of the service data packet to the first base station includes any one of a registration process, a tracking area update, a service request process, and an attachment process.
  • the mobility management device further includes:
  • the recording control unit is configured to delete the access node device corresponding to the marked IP address as the first base station or the second base station after a predetermined time after the marking unit marks the access node device corresponding to the IP address as the first base station or the second base station. Information of the second base station.
  • the mobility management device further includes:
  • the sending unit is configured to send the identified connection type to the gateway device.
  • an embodiment of the present invention also provides a method for performing access control on user equipment, including:
  • the policy control function device receives the connection type of the user equipment sent by the mobile management device;
  • the policy control function device issues a service quality policy or a charging control policy to the user equipment according to the connection type.
  • an embodiment of the present invention also provides a method for performing access control on user equipment, including:
  • the session management device receives the connection type of the user equipment sent by the mobile management device;
  • the session management device performs service quality control or charging control on the user equipment according to the connection type.
  • an embodiment of the present invention also provides a method for performing access control on user equipment, including:
  • the user plane function device receives the connection type of the user device sent by the mobile management device;
  • the user plane function device performs service quality control or charging control on the user equipment according to the connection type.
  • embodiments of the present invention also provide a network device, which may be any one of a mobile management device, a gateway device, a policy control function device, a session management device, and a user plane function device, including: processing The processor, the memory and the transceiver; the processor, the memory and the transceiver are connected in a communicative manner;
  • Program code is stored in the memory
  • the processor is configured to read the program code and cooperate with the transceiver to implement the functions of the method implemented by the mobile management device in the embodiment of the present invention.
  • an embodiment of the present invention also provides a computer storage medium
  • a program code is stored in the storage medium, and the program code includes program instructions that, when executed by a processor, cause the processor to cooperate with the transceiver to implement the function of any method in the embodiments of the present invention.
  • the embodiments of the present invention also provide a computer program product.
  • the above-mentioned computer program product contains program instructions.
  • the processor cooperates with the transceiver to implement the The function of any method implemented by any one of mobile management equipment, gateway equipment, policy control function equipment, session management equipment, and user plane function equipment.
  • the mobility management device may be a mobility management entity or an access management function device.
  • the gateway device may be a data gateway, a service gateway or a session management function device, a user plane function device, or a charging device.
  • the access type of the user equipment used by the gateway device, the policy control function device, the session management device, and the user plane function device may come from the access type determined by the mobile management device, and the user equipment For the identification method of the access type, reference may be made to the embodiment of the first aspect.
  • 1A-1E are network architecture diagrams of hybrid networking according to an embodiment of the present invention.
  • Figure 2 is a network architecture diagram of a 5G network according to an embodiment of the present invention.
  • FIG. 3 is a schematic flowchart of a method according to an embodiment of the present invention.
  • FIG. 4 is a schematic flowchart of a method according to an embodiment of the present invention.
  • FIG. 5 is a schematic flowchart of a method according to an embodiment of the present invention.
  • FIG. 6 is a schematic flowchart of a method according to an embodiment of the present invention.
  • FIG. 7 is a schematic flowchart of a method according to an embodiment of the present invention.
  • FIG. 8 is a schematic diagram of the structure of a network system according to an embodiment of the present invention.
  • FIG. 9 is a schematic structural diagram of a mobile management device according to an embodiment of the present invention.
  • FIG. 10 is a schematic diagram of the structure of a network device according to an embodiment of the present invention.
  • FIG. 1A-1E are schematic diagrams of five hybrid networking architectures. These hybrid networking architectures mix 4G access networks and 5G access networks. Among them, the architecture described in FIG. 1A-FIG. 1C and 1E may be referred to as a non-independent networking architecture.
  • the user equipment simultaneously establishes a connection with two access node devices (hereinafter referred to as access node or node device), namely access node 1 and access node 2, respectively; the service data of the user equipment can be passed through Either or both of the two access nodes perform forwarding.
  • access node device two access node devices
  • the user equipment may also only establish a connection with one access node.
  • the service gateway on the network side sends the service data packet to the access node 1, and the access node 1 divides part of the service according to the dual connection capability of the user equipment and the network status.
  • the data packet is shunted to the access node 2 and forwarded to the user equipment.
  • the service data is forwarded in the form of a data packet, so the service data may be referred to as a service data packet, which will not be described one by one in the subsequent embodiments.
  • the serving gateway shown in FIG. 1A, FIG. 1B, and FIG. 1C is a type of gateway device, and other gateway devices, such as data gateways, SMF devices, UPF devices, etc., will be mentioned in subsequent embodiments.
  • the service data packet is split to access node 1 and access node 2 at the service gateway, and then access node 1 and access node 2 respectively Forward to user equipment.
  • the network side sends service data packets to access node 2, and access node 2 can offload some service data packets to access node 1, and access node 1 will receive The service data packet is forwarded to the user equipment, and the access node 2 forwards the service data packet that is not shunted to the access node 1 to the user equipment.
  • the access node 1 that has a signaling interface with the mobility management device is called the primary access node, the first access node, or the primary access node
  • the device, the access node 2 that does not have a signaling interface with the mobility management device is called a secondary access node, a second access node, or a secondary access node device.
  • Access node 1 and access node 2 are nodes for user equipment to access the core network, where the primary access node may be a base station (for example, NodeB), and the secondary access node may be an evolved base station (evolved NodeB, eNB), The next generation NodeB (gNB) in the 5G mobile communication system or the base station in the future mobile communication system.
  • the mobile management device may be an MME
  • the serving gateway may be a serving gateway (serving gateway, S-GW)
  • the data gateway may be a packet data network gateway (packet data network gateway, PDN-GW).
  • the access node 1 and the access node 2 are connected to a 5G core network (5G Core, 5GC), and the user equipment can be connected to the access node 1 and the access node 2 at the same time.
  • the access node 1 may be an eNB supporting evolved LTE (evolved LTE, eLTE) access
  • the access node 2 may be a gNB supporting NR access.
  • Control plane signaling is transmitted to 5GC through gNB, that is, the signaling anchor point is at gNB.
  • the above-mentioned networking architecture can correspond to the option 4 networking mode.
  • the eNB may also directly connect to the 5GC without going through the gNB. In this case, it corresponds to the option 4a networking mode.
  • the access node 1 and the access node 2 are connected to a 5G core network (5G Core, 5GC), and the user equipment can be connected to the access node 1 and the access node 2 at the same time.
  • the access node 1 may be an eNB supporting evolved LTE (evolved LTE, eLTE) access
  • the access node 2 may be a gNB supporting NR access.
  • the control plane signaling is transmitted to the 5GC through the eNB, that is, the signaling anchor point is at the eNB.
  • the above-mentioned networking architecture can correspond to the option 7 networking mode.
  • the gNB can also be directly connected to the 5GC without going through the eNB. In this case, it corresponds to the option7a/7x networking mode.
  • the schematic diagram of the networking architecture shown in Figure 1A-1E can be applied to a 5G network;
  • the schematic diagram of the 5G network architecture shown in Figure 2 includes: user equipment, wireless network, and 5G core network; user equipment is connected through the current location The ingress node accesses the wireless network, and the core network equipment is used for user equipment registration, security authentication, mobility management, location management, session management, and forwarding of data packets between the user equipment and external data networks, etc.
  • the equipment included in the wireless network in Figure 2 may be a new radio (NR) equipment;
  • the core network equipment includes session management function (SMF) equipment, AMF equipment, and user plane function (UPF) ) Equipment, unified data management (UDM) equipment, policy control function (PCF) equipment, authentication service function (authentication server function, AUSF) equipment, network slice selection function (network slice selection function, NSSF equipment, network exposure function (NEF) equipment, network repository function (NRF) equipment, and application function (AF) equipment, etc., which are not specifically limited in the embodiment of the present application.
  • SMF session management function
  • AMF user plane function
  • UDM unified data management
  • PCF policy control function
  • authentication service function authentication server function
  • AUSF authentication service function
  • network slice selection function network slice selection function
  • NSSF network exposure function
  • NEF network repository function
  • AF application function
  • the NR device can correspond to the access node in Figures 1A to 1C
  • the access and mobility management function AMF can correspond to the mobility management device in Figures 1A to 1C
  • N1, N2, N3, N4, N9, N6, Nnssf, Nnef, Nnrf, Nnpcf, Nudm, Naf, Nausf, Namf, and Nsmf shown in FIG. 2 are all service-oriented interfaces, which will not be repeated here.
  • a dual-connected user equipment establishes a connection with two access nodes.
  • the user equipment is connected to two 5G base stations, namely: the primary access node and the secondary access node All are 5G base stations.
  • the primary access node may be an eNB
  • the secondary access node may be a gNB
  • the primary access node may be a next-generation base station gNB
  • the secondary access node may be an evolved base station eNB.
  • the embodiment of the present invention provides a method for identifying the access type of a user equipment.
  • access control can be performed, which may specifically include: mobile
  • the management device identifies the connection type used by the user equipment to access the core network through the access node device, and the connection type is single connection or dual connection; in the case that the connection type is single connection, the user equipment passes through one An access node device accesses the core network; in a case where the connection type is dual connectivity, the user equipment accesses the core network through two access node devices;
  • the mobility management device performs access control on the user equipment according to the connection type of the user equipment.
  • the method for the mobile management device to identify the connection type of the user equipment under different network architectures and the use after identification will be respectively described.
  • the identified use may include access restriction, charging strategy, service quality control strategy and license control on user equipment.
  • the master access node actively informs the mobile management equipment of the access type of the user equipment.
  • the access type can be an access node type or a wireless access type.
  • the mobile management equipment learns that the service data packet of the user equipment passes the master according to the access type. Whether the access node or the secondary access node forwards, it is learned that the user equipment is a single-connection user equipment or a dual-connection user equipment.
  • the establishment of the dual connection of the user equipment is determined by the main access node.
  • the main access node may trigger the addition, update, and deletion of the auxiliary access node, etc. Processes, which are used to establish, update, and delete forwarding channels for service data packets passing through the auxiliary access node.
  • the primary access node When the primary access node decides to forward a service data packet of a certain bearer of the user equipment by the secondary access node, the primary access node triggers the secondary access node addition process to establish a dual connection for the user equipment; or,
  • the primary access node When the user equipment has established dual connections and the primary access node decides to change a certain bearer service data packet of the user equipment from the primary access node to the secondary access node for forwarding, the primary access node triggers the update of the secondary access node The process is to switch the bearer to the secondary access node; or,
  • the primary access node When the user equipment has established a dual connection and the primary access node decides to change the service data packet forwarded by the secondary access node of the user equipment to the primary access node, the primary access node triggers the secondary access node deletion process.
  • the primary access node can Notifying the IP address and TEID of the primary access node or the secondary access node on the network side for receiving the service data packet, based on this, the process of the embodiment of the present invention may specifically be:
  • the master access node sends an evolved universal terrestrial radio access network radio access bearer (E-RAB) update instruction message to the mobile management device.
  • E-RAB update instruction message carries The IP address and TEID of the primary access node or secondary access node are used to notify the network to modify the forwarding channel of the downlink data packet.
  • the E-RAB update indication message may also carry an access type parameter
  • the access type parameter may be an access node type, such as NodeB, eNB, or gNB, etc.
  • the access type parameter may also be wireless access Type, such as evolved universal terrestrial radio access (E-UTRA) or NR, etc.
  • E-UTRA evolved universal terrestrial radio access
  • NR wireless access Type
  • the mobility management device After receiving the above-mentioned radio access bearer update request message, the mobility management device knows whether the service data packet corresponding to this bearer is forwarded by the primary access node or the secondary access node according to the access type parameters carried therein and the current networking mode.
  • the mobility management device learns that the access node that forwards the service data packet is the secondary access node. If the access type parameter is NodeB or E-UTRA, the mobility management device learns that the access node that forwards the service data packet is the primary access node. If the service data packet corresponding to any bearer of the user equipment is forwarded by the secondary access node, the mobility management device determines that the user equipment is a dual-connection user equipment; if all the service data packets corresponding to the bearer of the user equipment are forwarded by the primary access node, Then the mobile management device determines that the aforementioned user equipment is a single-connection user equipment.
  • the mobile management device can perform access control to the user equipment.
  • Specific access control such as:
  • the mobile management device Based on the dual-connection capability of the user equipment and the dual-connection capability in the subscription data, the mobile management device performs access control for users who have dual-connection capabilities but are currently single-connected, and the user equipment will not be able to use data services normally; or,
  • Separate license control for single-connected user equipment or dual-connected user equipment that is, separate and count the number of single-connected user equipment and the number of dual-connected user equipment.
  • the mobile management equipment issues an alarm or restricts the access of new user equipment.
  • the mobility management device sends a modify bearer request message to the serving gateway, and the update bearer request message carries the IP address and TEID of the primary access node or the secondary access node, and the radio access bearer update request The message also carries the aforementioned access type parameters.
  • the serving gateway After receiving the above-mentioned update bearer request message, the serving gateway stores the IP address and TEID of the access node carried therein.
  • the service data packet corresponding to the following bearer is sent by the serving gateway to the access node corresponding to the IP address and TEID.
  • the serving gateway may refer to the manner in which the mobile management device determines that the user equipment is a single-connection user equipment or a dual-connection user equipment according to the access type parameter, which will not be repeated here.
  • the service gateway can perform differentiated charging for the single-connection user equipment or the dual-connection user equipment. Even for the same user equipment, different charging can be performed for the service data packet forwarded by the primary access node and the service data packet forwarded by the auxiliary access node. For example, the charge rate of the service data packet forwarded by the secondary access node is lower than the charge rate of the service data packet forwarded through the main access node.
  • the serving gateway may send the access type parameters corresponding to the above bearers to the data gateway, and the data gateway may notify the connection type of the user equipment to the policy control function, so as to provide different services to the single connection user equipment or the dual connection user equipment Quality control or billing control.
  • the serving gateway replies with a modify bearer response (modify bearer response) message to the mobility management device for notifying the completion of the update of the downlink channel of the bearer.
  • modify bearer response modify bearer response
  • the mobility management device replies an E-RAB update indication confirmation (E-RAB modification indication confirmation) to the master access node to notify the completion of the update of the downlink channel of the bearer.
  • E-RAB update indication confirmation E-RAB modification indication confirmation
  • the main access node executes the process of establishing, updating, and deleting the forwarding channel that transmits service data packets through the auxiliary access node as an example, using the E-RAB update indication message to carry the access type parameters to the mobile management device; in addition, the main The access node can also use other messages in other processes to send the access type parameters to the mobility management device.
  • the primary access node uses a channel switching request message to notify the primary access node/secondary access
  • the IP address and TEID of the node, and the above-mentioned access type parameters are carried in the channel switching request message, so that the mobility management device and other devices in the network can determine whether the user equipment is a single-connection user equipment or a dual-connection user according to the access type parameters equipment.
  • this embodiment may be applicable to the networking architectures of FIGS. 1D and 1E. Please also refer to the 5G network architecture shown in FIG. 2.
  • the main access node uses the granularity of the quality of service flow (QoS Flow) to offload service data packets, and the main access node divides the service data packets corresponding to the quality of service flow (referred to as the service flow) to the main access node or
  • the IP address and TEID of the secondary access node are notified to AMF or SMF, so that AMF or SMF can determine the connection type of the user equipment, and perform different policy control on the user equipment according to the connection type.
  • the establishment of the dual connection of the user equipment is determined by the master access node.
  • the master access node may trigger the processes of adding, updating, and deleting auxiliary access nodes. It is used to establish, update and delete the forwarding channel of service data packets passing through the auxiliary access node.
  • the primary access node When the primary access node decides to forward the service data packet of a certain service flow (QoS Flow) of the user equipment by the secondary access node, the primary access node triggers the secondary access node addition process to establish dual connections for the user equipment; or,
  • the primary access node When the user equipment has established dual connections and the primary access node decides to forward the service data packets of a certain service flow of the user equipment to the secondary access node, the primary access node triggers the update process of the secondary access node, The service flow is switched to the auxiliary access node; or,
  • the primary access node When the user equipment has established a dual connection and the primary access node decides to change the service data packet of the user equipment forwarded by the secondary access node to be forwarded by the primary access node, the primary access node triggers the deletion process of the secondary access node.
  • the primary access node needs to notify the network side of the connection information of the main access node or the auxiliary access node (for example, used to receive the service data packet IP address and TEID).
  • the process of the embodiment of the present invention may specifically be:
  • the primary access node sends a PDU session resource update indication message to the access and mobility management function.
  • the PDU session resource update indication message carries the IP address of the primary or secondary access node and TEID, used to notify the access and mobility management functions to modify the forwarding channel of downlink data packets.
  • the PDU session resource update instruction message also carries an access type parameter
  • the access type parameter may be an access node type, such as eNB or gNB, etc.
  • the access type parameter may also be a wireless connection type, such as E -UTRA or NR, etc.
  • E-UTRA E-UTRA
  • NR NR
  • the access and mobility management function After the access and mobility management function receives the PDU session resource update indication message, it knows whether the service data packet of the above service flow is forwarded by the primary access node or the secondary access node according to the access type parameters and networking mode. If the user equipment has service data packets of any service flow that are forwarded by the auxiliary access node, the access and mobility management function determines that the user equipment is a dual-connection user equipment; if the service data packets of all service flows of the user equipment are transmitted by the master When the access node forwards, the access and mobility management function determines that the user equipment is a single-connection user equipment.
  • the access and mobility management functions can perform access control on the aforementioned user equipment based on the information that the aforementioned user equipment is a single-connection user equipment or dual-connection user equipment, such as:
  • access control is performed on the user equipment that has dual-connection capability but is currently single-connected, so that the user equipment will not be able to use data services normally; or,
  • the access and mobility management function sends a PDU session context update request (PDU session updatecontext request) message to the session management function.
  • PDU session updatecontext request PDU session updatecontext request
  • the PDU session context update request message carries the IP address and TEID of the primary access node or the secondary access node, and the PDU session context update request message also carries the access type parameter.
  • the PDU session context update request can be sent through the Nsmf interface.
  • the session management function can refer to the manner in which the access and mobility management functions determine whether the user equipment is a single-connection user equipment or a dual-connection user equipment according to the access type parameters, which will not be repeated here.
  • the session management function is based on the above information about whether the user equipment is single-connection user equipment or dual-connection user equipment. It can differentiate between single-connection user equipment or dual-connection user equipment for charging or service quality control. Even for the same user equipment, it can be The service data packet forwarded by the access node and the service data packet forwarded by the auxiliary access node are differentiated for charging or service quality control.
  • the session management function may notify the policy control function of the access type parameters corresponding to the service flow, so that the policy control function can perform different service quality control or charging control on the single-connection user equipment or the dual-connection user equipment.
  • the session management function sends an N4 session modification request message to the user plane function.
  • the N4 session modification request message carries the IP address and TEID of the primary or secondary access node.
  • the N4 session modification request message It also carries the access type parameter, so that the user plane function can perform different service quality control or charging control on the single-connection user equipment or the dual-connection user equipment.
  • the user plane function stores the IP address and TEID carried in the N4 session update request message, and subsequent service data packets of the service flow of the user equipment, the user plane function will send to the access node corresponding to the IP address and TEID.
  • the user plane function replies an N4PDU session update response (session modification response) message to the session management function.
  • the PDU session update response can be sent on the Nsmf interface.
  • the session management function replies a PDU session update context response (PDU session update context response) message to the access and mobility management function, which is used to notify the completion of the downlink channel update of the service flow.
  • PDU session update context response PDU session update context response
  • the access and mobility management function replies a PDU session resource update acknowledgement message to the master access node to notify the completion of the downlink channel update of the service flow.
  • the above process takes the process of establishing, updating and deleting the forwarding channel of the service data packet passing through the auxiliary access node as an example, using the PDU session resource update indication message to carry the access type parameters to the access and mobility management functions.
  • the primary access node can also use the channel switching request message to notify the IP address and TEID of the primary access node/secondary access node during the X2 handover process of the UE, and carry the access type in the channel switching request message
  • the parameters enable the access and mobility management functions and other devices in the network to determine the user equipment as a single-connection user equipment or a dual-connection user equipment.
  • the above provides a solution for the mobile management device to identify the connection type of the user equipment according to the access type parameter, and another solution for the mobile management device to identify the connection type of the user equipment is given below.
  • devices of the core network such as mobile management equipment (MME or AMF)
  • MME mobile management equipment
  • AMF mobile management equipment
  • a home subscriber server (home subscriber server, HSS) is responsible for the management and maintenance of user subscription information.
  • the home user server can also incorporate UDM functions.
  • the user equipment is turned on, initiates an attachment process, and sends an attachment request message to the mobility management device, and the attachment request message is forwarded to the mobility management device through the primary access node.
  • the attachment request message carries information about the dual connectivity capability of the user equipment, for example, the user equipment supports dual connectivity with NR capability with the new air interface.
  • the mobile management device sends a subscription data acquisition request to the HSS of the aforementioned user equipment.
  • the mobile management device receives the subscription data acquisition response returned by the HSS.
  • the subscription data acquisition response includes the subscription data of the user equipment, and the subscription data includes information about the dual connection capability of the user equipment.
  • the subscription data includes the new air interface auxiliary radio access type (NR as secondary radio access type, NR as secondary RAT) capability.
  • NR new air interface auxiliary radio access type
  • the mobile management device can identify the connection type of the user equipment through self-learning in the following ways:
  • the mobile management device recognizes a user equipment with dual-connection capability and dual-connection capability in the subscription data as a dual-connection user equipment.
  • the mobile management device may also identify the user equipment in combination with the local configuration, for example, identify the user equipment whose local configuration allows the establishment of dual connections as dual-connection user equipment. Identify the user equipment for which the local configuration does not allow the establishment of dual connections as single-connection user equipment.
  • the mobile management device can perform access control on the user equipment based on the information of the identified dual-connection user equipment or single-connection user equipment, such as:
  • Separate license control for single-connected user equipment or dual-connected user equipment that is, separate and count the number of single-connected user equipment and the number of dual-connected user equipment.
  • the mobile management equipment issues an alarm or restricts the access of new user equipment.
  • the mobile management device sends a session establishment request message to the serving gateway;
  • the session establishment request message carries a dual connectivity capability indication, such as dual connectivity with NR capability with the new air interface;
  • the serving gateway can identify the user equipment carrying the dual-connection capability indication as the dual-connection user equipment.
  • the serving gateway can perform differentiated charging for the single-connection user equipment or the dual-connection user equipment based on the above information about whether the user equipment is a dual-connection user equipment.
  • the serving gateway SGW sends a session establishment request message to the data gateway;
  • the session establishment request message carries a dual connectivity capability indication, such as dual connectivity with NR capability.
  • the data gateway PGW recognizes the user equipment carrying the dual-connection capability indication as the dual-connection user equipment.
  • the data gateway can perform differentiated charging or service quality control for single-connection user equipment or dual-connection user equipment based on the above-mentioned information about whether the user equipment is a dual-connection user equipment.
  • the data gateway may also send the dual-connection capability indication to the policy control function, so that the policy control function performs different service quality control or charging control on the single-connection user equipment or the dual-connection user equipment.
  • the data gateway replies with a session establishment response message to the serving gateway, and replies that the session between the serving gateway and the data gateway is successfully established.
  • the serving gateway replies a session establishment response message to the mobile management device, and replies that the session between the serving gateway and the mobile management device is successfully established.
  • the mobile management device sends an attach accept message to the user equipment to complete the attach process of the user equipment.
  • the mobility management device sends a modify bearer request message to the serving gateway to notify the serving gateway to establish a downlink tunnel for forwarding service data packets.
  • the specific process can be: the mobility management device sends an update bearer request message to the serving gateway, and the update bearer request message carries the IP address and TEID of the primary access node or the secondary access node; After the above-mentioned update bearer request message, the IP address and TEID of the access node carried therein are stored.
  • the serving gateway sends the service data packet corresponding to the aforementioned bearer to the access node corresponding to the aforementioned IP address and TEID.
  • the serving gateway replies with an update bearer response (modify bearer response) message to the mobility management device for notifying the completion of the update of the downlink channel of the above bearer.
  • the device in the core network can also identify the connection type of the user equipment.
  • the UE carries the aforementioned dual-connection capability indication in the tracking area update request message.
  • the mobility management device uses the similar self-learning method described above to identify the connection type of the user equipment.
  • the mobile management device may also send a session establishment request message to the serving gateway, which carries an indication of the dual connection capability of the user equipment.
  • the processing procedures and attachment procedures of the mobility management device, the serving gateway, and the data gateway are similar, and will not be repeated in this embodiment.
  • the master access node can trigger the flow reporting process of the dual-connected user equipment, The bearer forwarded by the secondary access node and the corresponding forwarded flow information are notified to the core network equipment including the mobility management equipment.
  • the primary access node sends a traffic usage report (secondary rat usage data report) message of the user equipment to the mobility management device, and the traffic usage report message carries a bearer identifier and corresponding traffic information.
  • a traffic usage report secondary rat usage data report
  • the mobility management device determines that the user equipment is a dual-connection user equipment according to it. If there is only traffic information forwarded by the main access node in the traffic usage report, the mobility management device determines that the user equipment is a single-connection user equipment.
  • the flow information of the user equipment includes the flow information of the uplink and downlink data packets of the user equipment.
  • the mobile management device can perform access control on the user equipment, such as:
  • Separate license control for single-connected user equipment or dual-connected user equipment that is, separate and count the number of single-connected user equipment and the number of dual-connected user equipment.
  • the mobile management equipment issues an alarm or restricts the access of new user equipment.
  • the mobile management device sends a traffic report notification message to the serving gateway.
  • the serving gateway may refer to a manner in which the mobile management device determines that the user equipment is a single-connection user equipment or a dual-connection user equipment according to the traffic report notification message.
  • the service gateway can perform differentiated charging for single-connection user equipment or dual-connection user equipment; for the same user equipment, it can also perform service data forwarded by the main access node Packets and service data packets forwarded by the auxiliary access node are charged separately.
  • the serving gateway sends the foregoing traffic report notification message to the data gateway.
  • the data gateway may refer to the manner in which the access and mobility management device determines whether the user equipment is a single-connection user equipment or a dual-connection user equipment according to the traffic report notification message, which will not be repeated here.
  • the data gateway can perform differentiated charging or service quality control on the single-connection user equipment or the dual-connection user equipment.
  • the data gateway may also send traffic report notification messages to the policy control function, so that the policy control function performs different service quality control or charging control on the single-connection user equipment or dual-connection user equipment.
  • the data gateway replies with a change notification ACK message
  • the serving gateway replies with a change notification confirmation message.
  • the above-mentioned traffic report notification message may be reported through a dedicated process, or may be reported in a signaling message of the current process, which does not affect the implementation of this embodiment, and will not be repeated here.
  • the foregoing current process may be: handover, registration update, service request, PDU session update/delete, tracking area update, proprietary bearer update/delete, etc.
  • the mobility management device receives the traffic usage report reported by the master access node within the connected state period of the user equipment, the mobility management device still marks the user equipment as a dual-connected user equipment after the S1 release process. If the mobility management device does not receive the traffic usage report reported by the master access node during the connected state period, the user equipment is marked as a single-connection user equipment after the S1 release process.
  • the connection type of the user equipment after the connection type of the user equipment has been known, the user's connection type can be determined by whether the main access node reports a traffic usage report during the connected state period, without consuming additional signaling or transmitting additional data. , Saving network resources.
  • the primary access node can trigger the flow reporting process of the dual-connection user equipment, and the primary access node will forward services through the secondary access node Flow and traffic report notification to core network equipment including access and mobility management functions.
  • the primary access node sends a traffic usage report (secondary rat usage data report) message to the access and mobility management function.
  • the traffic report notification message carries the service flow identifier (QoS flowID, QFI) and corresponding traffic information .
  • the access and mobility management function determines that the user equipment is a dual-connection user equipment based on the above-mentioned traffic report notification message, and can perform access control on the user equipment, such as:
  • the access and mobility management function sends a PDU session context update request (PDU session_updatecontextrequest) to the session management function.
  • PDU session_updatecontextrequest PDU session_updatecontextrequest
  • the traffic report notification message carries the service flow identifier obtained in 701 and its corresponding flow information.
  • the PDU update session management context request is sent using the Nsmf interface.
  • the session management function can refer to the manner in which the access and mobility management function determines the user equipment as a single-connection user equipment or dual-connection user equipment according to the traffic report notification message, which is not repeated here.
  • the session management function is based on the information that the above-mentioned user equipment is a single-connection user equipment or a dual-connection user equipment, and can distinguish between single-connection user equipment and dual-connection user equipment and service quality control; in addition, for the same user equipment,
  • the service data packet forwarded by the main access node and the service data packet forwarded by the auxiliary access node are differentiated, charging and service quality control.
  • Session management device PDU session context update response (PDU session_update context response).
  • the PDU update session management context response can be sent using the Nsmf interface.
  • the above-mentioned traffic report can be reported through the enumerated proprietary process, or can be reported in the signaling message of the current process, which does not affect the implementation of this embodiment, and will not be repeated here.
  • the above proprietary process refers to the process of issuing a change notification request; the foregoing current process can be: handover, registration update, service request, PDU session update/delete, tracking area update, proprietary bearer update/delete, etc.
  • the access and mobility management function receives the Secondary RAT Usage Data Report from the primary access node during the connected state period of the user equipment, the access and mobility management function will release the above-mentioned users after the N2 release process.
  • the device is marked as a dual connection user device. If the access and mobility management function does not receive the Secondary RAT Usage Data Report reported by the primary access node during the connected state period, the above-mentioned user equipment is marked as a single-connection user equipment after the N2 Release process.
  • the embodiment of the present invention also provides a method for the network side device to self-learn and mark the access node type, and to determine the connection type of the user equipment based on the method, specifically as follows:
  • the mobility management device forwards it to the serving gateway.
  • the mobility management device can first mark the access node corresponding to the IP address, as follows:
  • the mobile management device After the mobile management device confirms whether the user equipment is allowed to use dual connections, for user equipment that does not allow dual connections, that is, single-connection user equipment, the IP address and TEID of the access node received by the mobile management device should be the master The access node is assigned, so the mobility management device can mark the access node corresponding to this IP address as the primary access node or the first base station.
  • the main access node first establishes the forwarding channel of the carried service data packet to the main connection
  • the IP address and TEID of the access node sent to the mobility management device should be assigned to the main access node. Therefore, in these specific procedures, after the mobility management device receives the IP address and TEID of the access node, it marks the access node corresponding to the received IP address as the first base station; or more specifically, the 4G base station, eNodeB, the primary access node or the first access node. That is, after receiving the initial context response message sent by the access node, the mobility management device obtains the IP address and TEID of the access node carried in the message, and marks the access node corresponding to this IP address as the first base station.
  • the mobility management device After the mobility management device confirms that the connection type of the user equipment is dual-connection user equipment, it can mark the IP address of the new access node as the second base station, or more specifically: 5G base station, gNB or, eNB, or secondary access node. Or, if the mobility management device receives the IP addresses of multiple access nodes, it marks the access node corresponding to the user plane IP address of the same user equipment different from the user plane IP address marked as the first base station as the second base station.
  • the E-RAB update indication message since the E-RAB indication message is sent for dual-connection user equipment, after the mobility management device receives the E-RAB update indication message, the E-RAB update indication message carries the IP of the access node Address and TEID. Since there is already an IP address marked as the first base station, and the IP address of the access node carried in the current E-RAB update indication message is different from the IP address of the first base station already marked, the mobility management device will receive a new The access node corresponding to the IP address in the received E-RAB update instruction message is marked as the second base station.
  • the mobility management device uses the above three methods to mark the base station type.
  • the mobility management device can set an aging timer for this purpose. After the aging timer expires, the marked base station type is cleared, and the learning process of this embodiment is executed again.
  • the mobility management device can learn the bearers established by the user equipment, which ones are established on the primary access node and which ones are established on the secondary access node. Accordingly, the mobility management device can identify the connection type of the user equipment, specifically: when the user equipment has any bearer established on the secondary access node, the mobility management device determines that the user equipment is a dual-connection user equipment; When both are established at the main access node, the mobility management device determines that the user equipment is a single-connection user equipment.
  • the mobile management device can notify the identification result to the service gateway, data gateway, policy control function and other equipment, such as identifying the access point type Send to the service gateway, data gateway and policy control function.
  • the information that the user equipment is a single-connection user equipment or a dual-connection user equipment is notified to devices such as a service gateway, a data gateway, and a policy control function through a signaling message.
  • the access and mobility management function forwards it to the session management function. Forward to the user plane function.
  • the access and mobility management functions can first mark the access node corresponding to the IP address, as follows:
  • the main access node first establishes the forwarding channel of the service data packet related to the service flow to the local, and therefore sends it to the IP of the access node of the access and mobility management function
  • the address and TEID are assigned by the master access node. Therefore, after the access and mobility management function receives the IP address and TEID of the access node in the above specific process, it marks the access node corresponding to the received IP address as the first base station.
  • the access and mobility management function receives the initial context response message sent by the access node, obtains the IP address and TEID of the access node carried in the message, and marks the access node corresponding to the IP address as the first base station .
  • the access and mobility management function can mark the second base station as the second base station after receiving the IP address of the new access node after confirming that the connection type of the user equipment is dual-connected user equipment; or, if the access and mobility management After the function receives the IP addresses of multiple access nodes, it marks the access node corresponding to the user plane IP address of the same user equipment that is different from the user plane IP address marked as the first base station as the second base station.
  • the PDU session resource update indication message in Figure 4 is sent for dual-connected user equipment.
  • the access and mobility management function After the access and mobility management function receives the PDU session resource update indication message, it can use the PDU session resource update indication message Obtain the IP address and TEID of the access node. If there is already an IP address marked as the first base station, and the IP address of the access node carried in the current message is different from the IP address already marked as the first base station, then carry the PDU session resource update indication message The access node corresponding to the IP address of is marked as the second base station.
  • the access and mobility management functions use the above two methods to mark the base station type.
  • the access and mobility management function can be used to set an aging timer for this purpose. After the aging timer expires, the marked base station type is cleared and executed again The learning process of this embodiment.
  • the access and mobility management function knows which service flows established by the user equipment are established on the primary access node and which are established on the secondary access node. Accordingly, the access and mobility management functions can refer to the aforementioned method for the mobility management device to identify the connection type of the user equipment, which will not be repeated here.
  • the recognition result may be notified to the session management device, the user plane function, and the policy control function.
  • the identified access point type is sent to the session management device, the user plane function, and the policy control function; another example is to notify the session management device of the information that the user is a single-connection user equipment or a dual-connection user equipment through a signaling message.
  • User plane functions and policy control functions are examples of policy control functions.
  • the present application also provides a network system, as shown in FIG. 8, including: a mobile management device 801 and a gateway device 802; the network architectures shown in FIG. 1A, FIG. 1B, FIG. 1C, and FIG. 2 can be referred to together;
  • the mobility management device 801 is configured to execute the method flow performed by the mobility management device provided in the first aspect of the embodiment of the present invention, and more specifically, for example, the procedures executed by the mobility management device in FIG. 3, FIG. 5, and FIG. 6 Method flow, the method flow executed by the access and mobility management functions in Figure 4;
  • the gateway device 802 is configured to perform service quality control or charging control on the user equipment according to the connection type received from the mobility management device.
  • the mobile management device identifies the connection type of the user equipment and informs the gateway device, and the gateway device can perform different service quality control and charging control on user equipment of different connection types accordingly.
  • the network system further includes a policy control function device 803, a session management device 804, or a user plane function device 805;
  • the mobile management device 801 is further configured to send the connection type to the policy control function device 803, the session management device 804, or the user plane function device 805;
  • the policy control function device 803 is configured to issue a quality of service policy or a charging control policy to the user equipment according to the connection type; or,
  • the session management device 804 is configured to perform service quality control or charging control on the user equipment according to the connection type; or,
  • the user plane function device 805 is configured to perform service quality control or charging control on the user equipment according to the connection type.
  • the mobile management device identifies the connection type of the user equipment and then informs other various network devices (policy control function device 803, session management device 804 or user plane function device 805, etc.), and the network device can use it according to its own
  • policy control function device 803, session management device 804 or user plane function device 805, etc. the network device can use it according to its own
  • the functions in charge perform different controls to achieve differentiated services for user equipment of different connection types.
  • the embodiment of the present invention also provides a mobile management device, as shown in FIG. 9, including:
  • the identification unit 901 is configured to identify the connection type used by the user equipment to access the core network through the access node device, and the connection type is single connection or dual connection; in the case that the connection type is single connection, the user The device accesses the core network through one access node device; when the connection type is dual connectivity, the user equipment accesses the core network through two access node devices; and
  • the access control unit 905 is configured to perform access control on the user equipment according to the connection type of the user equipment.
  • the mobile management device identifies the connection type of the user equipment, and the identification function can be gathered in a fixed device; in addition, the mobile management device is the core network device that the user equipment first accesses via the access node device Therefore, if the mobile management device further performs targeted services such as access control, it is more timely and the delay is smaller than the notification to the mobile management device after being identified by other devices.
  • the identification unit 901 is configured to determine the connection type of the user equipment according to the access type parameter of the user equipment sent by the access node device, and the access type parameter is used for Indicating the wireless access type of the user equipment or the type of the access node device;
  • receiving a message carrying the Internet Protocol IP address of the access node device and determining the connection type of the user equipment according to the IP address of the access node device.
  • the identification unit 901 is configured to determine the connection type of the user equipment according to the access type parameter of the user equipment sent by the access node device, including: The sent radio access bearer update request message, or channel switching request message, or the access type parameter included in the notification message of the service flow determines the connection type of the user equipment.
  • the identification unit 901 is configured to receive a message carrying the Internet Protocol IP address of the access node device, and determine the connection type of the user equipment according to the IP address of the access node device Including: receiving initial context establishment response message, packet data unit PDU session resource establishment response message or default bearer establishment response message, carried in the initial context establishment response message, PDU session resource establishment response message or default bearer establishment response message
  • the IP address of the access node device; the connection type of the user equipment is determined according to the IP address of the access node device.
  • the identification unit 901 is configured to determine according to one or more of the dual connectivity capability of the user equipment, the subscription information of the user equipment, and the local configuration of the mobility management device
  • the connection types of the user equipment include:
  • the identification unit 901 is configured to receive a data usage report sent by the access node device, where the data usage report contains traffic information of the user equipment, and the mobility management device
  • the data usage report determining the connection type of the user equipment includes: determining that the data usage report sent by the access node device is received within the connected state period of the user equipment, and then determining that the connection type of the user equipment is dual connection. On the other hand, if it is determined that within the connected state period of the user equipment, the data usage report sent by the access node device is not received, then it is determined that the connection type of the user equipment is single connection.
  • the mobility management device further includes:
  • the marking unit 903 is configured to distinguish the access node device as the first base station or the second base station according to the received IP address of the access node device;
  • the identification unit 901 is specifically configured to: when the access node device accessed by the user equipment includes a first base station and a second base station, the mobility management device determines that the connection type of the user equipment is dual connection; When the access node device accessed by the user equipment includes only the first base station, the mobility management device determines that the connection type of the user equipment is single connection.
  • the marking unit 903 is configured to, when the user equipment is not allowed to establish dual connections, after the mobility management device receives the IP address of the access node device, Mark the access node device corresponding to the IP address of the access node device as the first base station; obtain the IP address of the access node device received in the process of establishing the forwarding channel of the service data packet to the first base station, and transfer the The access node device corresponding to the IP address of the access node device is marked as the first base station; when the user equipment accesses two IP addresses, and the access node device corresponding to one of the IP addresses is the first base station, all The access node device corresponding to the other of the two IP addresses is marked as the second base station.
  • the process of establishing the forwarding channel of the service data packet to the first base station first includes:
  • Any one of the registration process, tracking area update, service request process, and attachment process is any one of the registration process, tracking area update, service request process, and attachment process.
  • the mobility management device further includes:
  • the recording control unit 904 is configured to delete the access node device corresponding to the marked IP address as the first base station or the second base station after a predetermined time after the marking unit 903 marks the access node device corresponding to the IP address as the first base station or the second base station. Information of the base station or the second base station.
  • the mobility management device further includes:
  • the sending unit 902 is configured to send the identified connection type to the gateway device.
  • the identification unit 901 and other units except the sending unit 902 can correspond to related functions of the processor of the mobility management device in the subsequent embodiments, and the sending unit 902 can correspond to related functions of the transceiver.
  • the embodiment of the present invention also provides a network device, which may be any one of a mobile management device, a gateway device, a policy control function device, a session management device, and a user plane function device.
  • the network device includes: a processor 1001, a memory 1002, and a transceiver 1003; the processor 1001, the memory 1002, and the transceiver 1003 are connected in a communicative manner;
  • Program codes are stored in the memory 1002;
  • the processor 1001 is used to read the program code and cooperate with the transceiver 1003 to implement the embodiment provided by the first aspect of the embodiment of the present invention, except that the gateway device sends and receives messages
  • the processor 1001 can correspond to the functions of the identification unit 901, the marking unit 903, the recording control unit 904, and the access control unit 905 in the structure shown in FIG. 9.
  • the specific execution process is not detailed in this embodiment. Narrated.
  • the transceiver 1003 may correspond to the function of the sending unit 902 in the structure shown in FIG. 9, and the specific execution process will not be described in detail in this embodiment.
  • the transceiver 1003 is used to receive the connection type of the user equipment sent by the mobile management device; the processor 1001 is used according to the user equipment
  • the access type provides corresponding differentiated services to user equipment.
  • the policy control function device issues a quality of service policy or a charging control policy to the user equipment according to the connection type.
  • the session management device performs service quality control or charging control on the user equipment according to the connection type.
  • the user plane function device performs service quality control or charging control on the user equipment according to the connection type.
  • the gateway device performs service quality control or charging control on the user equipment according to the connection type.
  • the memory 1002 includes but is not limited to random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (erasable programmable read only memory, EPROM), or A portable read-only memory (compact disc read-only memory, CD-ROM), the memory 1002 is used for related instructions and data.
  • the transceiver 1003 is used to receive and send data and messages.
  • the processor 1001 may be one or more central processing units (CPUs). In the case where the processor 1001 is a CPU, the CPU may be a single-core CPU or a multi-core CPU.
  • the embodiment of the present invention also provides a computer storage medium, the storage medium stores program code, the program code includes program instructions, the program instructions when executed by the processor, the processor and the transceiver cooperate
  • the storage medium stores program code
  • the program code includes program instructions
  • the program instructions when executed by the processor, the processor and the transceiver cooperate
  • the embodiment of the present invention also provides a computer program product.
  • the above-mentioned computer program product contains program instructions.
  • the processor and the transceiver cooperate to realize any item provided in the embodiments of the present invention.
  • the function of the method please refer to the method flow in the previous article for details, which will not be detailed here.
  • the process can be completed by a computer program instructing relevant hardware.
  • the program can be stored in a computer readable storage medium. , May include the processes of the foregoing method embodiments.
  • the aforementioned storage media include: ROM or random storage RAM, magnetic disks or optical discs and other media that can store program codes.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Computer Security & Cryptography (AREA)
  • Quality & Reliability (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本发明实施例公开了一种对用户设备进行接入控制的方法，网络系统及相关产品，其中方法包括：移动管理设备识别用户设备通过接入节点设备接入核心网所采用的连接类型，所述连接类型为单连接或双连接；在所述连接类型为单连接的情况下，所述用户设备通过一个接入节点设备接入所述核心网；在所述连接类型为双连接的情况下，所述用户设备通过两个接入节点设备接入所述核心网；所述移动管理设备依据所述用户设备的连接类型，对所述用户设备进行接入控制。本发明实施例，将识别功能聚集在一个固定的设备中，在移动管理设备进行接入控制等针对性服务，更为及时，延迟更小。

Description

对用户设备进行接入控制的方法，网络系统及相关设备
本申请要求于2019年8月2日提交中国国家知识产权局、申请号为201910713959.2、发明名称为“对用户设备进行接入控制的方法，网络系统及相关设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明涉及通信技术领域，尤其涉及一种对用户设备进行接入控制的方法，网络系统及相关设备。
背景技术
移动通信网络支持非独立组网架构；在非独立组网架构中，用户设备可以同时与两个接入节点建立连接；用户设备的业务数据可以通过这两个接入节点中的任意一个或两个进行转发。在非独立组网架构中，用户设备也可以仅与一个接入节点建立连接。
用户设备与两个接入节点建立连接，该用户设备可以称为双连接用户设备，该用户设备的连接类型为双连接；用户设备仅与一个接入节点建立连接，该用户设备可以称为单连接用户设备，该用户设备的连接类型为单连接。
在目前的移动通信网络中，没有识别用户设备的连接类型的技术方案，无法对对用户设备进行接入控制的。
发明内容
本发明实施例所要解决的技术问题在于提供一种对用户设备进行接入控制的方法，网络系统及相关产品，用于识别用户设备的连接类型，为针对性的服务提供支撑。
第一方面，本发明实施例提供了一种对用户设备进行接入控制的方法，该方法包括：
移动管理设备识别用户设备通过接入节点设备接入核心网所采用的连接类型，所述连接类型为单连接或双连接；在所述连接类型为单连接的情况下，所述用户设备通过一个接入节点设备接入所述核心网；在所述连接类型为双连接的情况下，所述用户设备通过两个接入节点设备接入所述核心网；
所述移动管理设备依据所述用户设备的连接类型，对所述用户设备进行接入控制。
在本实施例可以应用于非独立组网或者独立组网的移动通信网络；其中，接入节点设备可以称为接入节点，例如第四代(4G)网络或第五代(5G)网络中的基站；同一个用户设备可以接入两个基站，如主接入节点和辅接入节点。移动管理设备可以为移动管理实体(mobility management entity，MME)或接入和移动性管理功能(access and mobility management function，AMF)设备。
在本实施例中，移动管理设备对用户设备进行接入控制可以是移动管理设备按照连接类型，在确定用户设备有双连接能力或者签约了双连接，当前该用户设备如果使用单连接，则对其进行接入控制，使该用户设备不能使用业务数据；或者，对单连接用户设备或者多 连接用户设备分别进行不同的许可控制。具体过程本发明实施例不作唯一性限定。
由于一个用户设备会对应一个移动管理设备，可能对应多个网关设备或其网络设备，因此本实施例通过移动管理设备识别用户设备的连接类型，可以将识别功能聚集在一个固定的设备中；另外，移动管理设备是用户设备经接接入节点设备首先接入的核心网设备，因此如果在移动管理设备进行接入控制等针对性服务，相比于由其他设备识别后再通知移动管理设备更为及时，延迟更小。
在一个可能的实现方式中，所述移动管理设备识别用户设备通过接入节点设备接入核心网所采用的连接类型包括：
所述移动管理设备接收接入节点设备发送的所述用户设备的接入类型参数，所述接入类型参数用于指示所述用户设备的无线接入类型或所述接入节点设备的类型；所述移动管理设备根据所述接入类型参数确定所述用户设备的连接类型；
或者，所述移动管理设备根据所述用户设备的双连接能力、所述用户设备的签约信息以及所述移动管理设备的本地配置中的一项或多项，确定所述用户设备的连接类型；
或者，所述移动管理设备根据接收所述接入节点设备发送的数据使用报告，所述数据使用报告中包含用户设备的流量信息，所述移动管理设备根据所述数据使用报告确定所述用户设备的连接类型；
或者，所述移动管理设备接收携带所述接入节点设备的互联网协议(internet protocol，IP)地址的消息，所述移动管理设备根据所述接入节点设备的IP地址确定所述用户设备的连接类型。
在本实施例中提供了多种可选方法，由移动管理设备确定用户设备的连接类型。
第一种方法主要由接入节点设备通过消息发送接入类型参数给移动管理设备，移动管理设备根据接入类型参数来确定用户设备的连接类型。其中，携带该接入类型参数的消息可以是在建立、更新、删除与上述用户设备相关的承载的流程中所使用的消息中，例如：无线接入承载的更新请求消息等，也可以使用专用的消息来携带该接入类型参数，本实施例对此不作唯一性限定。另外，该接入类型参数指示用户设备的无线接入类型或者接入节点设备的类型的具体手段，可以是直接指示，也可以是移动管理设备所能识别的参数通过判断得出，具体形式本发明实施例不作唯一性限定。该第一种方法，移动管理设备可以从携带的信息中直接获得用户设备的连接类型，效率较高。
第二种方法主要由移动管理设备获得确定连接类型所需的参数，然后据此确定用户设备的连接类型。其中，用户设备的双连接能力可以由用户设备进行网络注册时上报；用户的签约信息中也可以携带该用户设备是否允许使用双连接的信息，移动管理设备可以从保存有签约信息的设备例如归属用户服务器中获得；移动管理设备的本地配置也可以包含是否允许该用户设备使用双连接的信息；移动管理设备可以根据用户设备的双连接能力、用户的签约信息、本地配置等其中的一项或者多项确定连接类型。该第二种方法，移动管理设备可以相对于前述第一种方法间接获得较为准确的用户设备的连接类型，可以进一步减少信令的使用以及数据的传递。
第三种方法主要由单连接或双连接对数据使用报告的影响来确定；第四种则是通过IP地址来区分不同的接入节点设备的类型，例如第一基站或第二基站，其中第一基站可 以为4G基站，第二基站可以为5G基站，或者第一基站和第二基站可以都为5G基站；据此来确定用户设备的连接类型。在基于4G核心网的非独立组网的场景下，双连接的用户设备接入第一基站和第二基站分别为4G基站和5G基站，在基于5G核心网的组网场景下，双连接的用户设备接入第一基站和第二基站都为5G基站。该第三种方法，提供了由移动管理设备智能化的识别用户设备的连接类型的实现手段，不必依赖于已经存在或传递的用于识别用户设备的连接类型的数据。
在一个可能的实现方式中，主接入节点(或称为第一接入节点、主接入节点设备)、eNodeB以及4G基站统称为第一基站；辅接入节点(或第二接入节点、辅接入节点设备)、下一代基站(next generation NodeB，gNB)，演进型基站(evolved NodeB，eNB)以及5G基站统称为第二基站。
在一个可能的实现方式中，所述移动管理设备接收接入节点设备发送的所述用户设备的接入类型参数；所述移动管理设备根据所述接入类型参数确定所述用户设备的连接类型，具体包括：
所述移动管理设备接收接入节点设备发送的无线接入承载更新请求消息，或通道切换请求消息，或业务流的通知消息；在所述无线接入承载更新请求消息，或所述通道切换请求消息，或所述业务流的通知消息中包含所述接入类型参数；所述移动管理设备根据所述接入类型参数确定所述用户设备的连接类型。
本实施例提供了几种可能用于携带接入类型参数的具体消息举例，使用以上举例中的消息携带接入类型参数可以不必新增信令，与已有的流程有较好的兼容性。
在一个可能的实现方式中，所述移动管理设备接收携带所述接入节点设备的互联网协议IP地址的消息，所述移动管理设备根据所述接入节点设备的IP地址确定所述用户设备的连接类型包括：
所述移动管理设备接收初始上下文建立响应消息，分组数据单元(packetdata unit，PDU)会话资源建立响应消息或者缺省承载建立响应消息，在所述初始上下文建立响应消息，PDU会话资源建立响应消息或者缺省承载建立响应消息中携带所述接入节点设备的IP地址，所述移动管理设备根据所述接入节点设备的IP地址确定所述用户设备的连接类型。
本实施例提供了几种由接入节点设备发送接入类型参数给移动管理设备的具体消息举例，可以理解的是在其他消息中携带，或者使用专用消息发送并不会影响本发明实施例的实现。使用以上消息，可以不必增加新的消息类型，可以及时上报接入类型参数，或接入类型参数的变化，使移动管理设备能准确且及时确定用户设备的连接类型。
在一个可能的实现方式中，所述移动管理设备根据所述用户设备的双连接能力、所述用户设备的签约信息以及所述移动管理设备的本地配置的一项或多项，确定所述用户设备的连接类型包括：
所述移动管理设备接收所述用户设备发送的所述用户设备的双连接能力的信息；所述移动管理设备根据所述用户设备的双连接能力的信息，确定所述用户设备的连接类型，或者，
所述移动管理设备从所述用户设备的归属用户服务器获取所述用户设备的签约信息，根据所述签约信息确定所述用户设备的连接类型，或者，
所述移动管理设备获取所述移动管理设备的本地配置，在所述本地配置中包含是否允许所述用户设备建立双连接的信息；依据所述本地配置确定所述用户设备的连接类型。
在本实施例中，如果用户设备有双连接能力，则可以确定该用户设备的连接类型为双连接，否则为单连接；签约信息中如果包含用户设备具有双连接能力的信息，则可以确定该用户设备的连接类型为双连接，否则为单连接；上述本地配置如果允许用户设备采用双连接，则确定该用户设备的连接类型为双连接，否则为单连接；也可以综合以上三个因素，全部为是则确定为双连接，否则为单连接，或者其中一个为是则确定为双连接，否则为单连接，或者全部为是则确定为双连接，全部为否则确定为单连接，其他情况确定无法确定连接类型。
在一个可能的实现方式中，所述移动管理设备根据接收所述接入节点设备发送的数据使用报告，所述数据使用报告中包含用户设备的流量信息，所述移动管理设备根据所述数据使用报告确定所述用户设备的连接类型包括：
所述移动管理设备确定在所述用户设备的连接态周期内，接收到所述接入节点设备发送的数据使用报告，则确定所述用户设备的连接类型为双连接。
另一方面，如果所述移动管理设备确定在所述用户设备的连接态周期内，没有接收到所述接入节点设备发送的数据使用报告，则确定所述用户设备的连接类型为单连接。
本实施例通过连接态周期内是否收到接入节点设备发送的数据使用报告来确定用户设备的连接类型，不必为了确定用户设备的连接类型而额外消耗信令。
在一个可能的实现方式中，所述移动管理设备根据接收的接入节点设备的IP地址，确定所述用户设备的连接类型包括：
所述移动管理设备根据接收的接入节点设备的IP地址，将接入节点设备区分为第一基站或第二基站；
在所述用户设备接入的接入节点设备包含第一基站和第二基站时，所述移动管理设备确定所述用户设备的连接类型为双连接；
在所述用户设备接入的接入节点设备只包含第一基站时，所述移动管理设备确定所述用户设备的连接类型为单连接。
在本实施例中，移动管理设备可以根据IP地址来确定接入节点设备的类型是第一基站还是第二基站，随后再依据用户设备接入到何种类型的接入节点设备来确定连接类型。该IP地址可以是按照已有流程上报给移动管理设备的，因此不必消耗额外的信令，节省了信令开销。
在一个可能的实现方式中，所述移动管理设备根据接收的接入节点设备的IP地址，将接入节点设备区分为第一基站或第二基站，包括：
在所述用户设备不被允许建立双连接的情况下，所述移动管理设备在接收到所述接入节点设备的IP地址后，将所述接入节点设备的IP地址对应的接入节点设备标记为第一基站；
所述移动管理设备在业务数据包的转发通道建立到第一基站的流程中接收接入节点设备的IP地址，将所述接入节点设备的IP地址对应的接入节点设备标记为第一基站；
所述移动管理设备在所述用户设备接入两个IP地址，且其中一个IP地址对应的接入 节点设备为第一基站时，将所述两个IP地址中的另一IP地址对应的接入节点设备标记为第二基站。
本实施例在移动管理设备一侧，通过对收到的IP地址的分析标记了接入节点所属的基站类型，可以准确识别出不同类型的基站。
在一个可能的实现方式中，所述业务数据包的转发通道建立到第一基站的流程包括：
注册流程、跟踪区域更新、服务请求流程以及附着流程中的任意一项。
本实施例提供了如何标记接入节点设备的类型的具体实现手段。其中，用于用户设备不被允许建立双连接的情况，可以是移动管理设备的本地配置上述用户设备不具有双连接能力，或者其他原因导致其不能建立双连接的情况；由于特定流程中，如跟踪区域更新、服务请求流程以及附着流程等，主接入节点通常将承载的业务数据包的转发通道先建立到主接入节点上，即发送给移动管理设备的接入节点的IP地址和隧道端点标识(tunnel endpoint identifier，TEID)通常为主接入节点分配的，因此可以标记为第一基站；由于双连接的场景下，通常是一个第一基站，另一个为第二基站，因此在确定其中一个为第一基站的情况下，另一个为第二基站。本实施例可以在不增加网络开销的情况下，准确标记不同类型的基站，为识别用户设备的连接类型提供依据。
在一个可能的实现方式中，所述方法还包括：
所述移动管理设备在标记IP地址对应的接入节点设备为第一基站或第二基站后的预定时间之后，删除标记的IP地址对应的接入节点设备为第一基站或第二基站的信息。
在本实施例中，设置的预定时间为老化时间，可以使用老化定时器来实现计时，在某一个IP地址被标记后，定时器超时则删掉该IP地址的标记，可以确保标记的准确性。
在一个可能的实现方式中，所述方法还包括：
所述移动管理设备向网关设备发送识别的所述连接类型。
在本实施例中，网关设备可以包括4G网络中的服务网关(serving gateway，SGW)、数据网关(PDN gateway，PGW)、5G网络中的会话管理功能(session management function，SMF)设备、用户面功能(user plane function，UPF)设备等。移动管理设备将连接类型发往网关设备后，可以为网关设备执行服务质量控制或者计费控制提供依据。
第二方面，本发明实施例还提供了一种连接类型的识别方法，包括：
接入节点设备确定用户设备的接入类型参数，向移动管理设备发送用户设备的接入类型参数，所述接入类型参数用于指示所述用户设备的无线接入类型或所述接入节点设备的类型；
所述移动管理设备接收所述接入节点设备发送的所述用户设备的接入类型参数，根据所述接入类型参数确定所述用户设备的连接类型。
在一个可能的实现方式中，所述向移动管理设备发送用户设备的接入类型参数包括：
所述接入节点设备向所述移动管理设备发送无线接入承载更新请求消息，或通道切换请求消息，或业务流的通知消息；在所述无线接入承载更新请求消息，或所述通道切换请求消息，或所述业务流的通知消息中包含所述接入类型参数。
第三方面，本发明实施例还提供了一种网络系统，包括：移动管理设备和网关设备；
所述移动管理设备，用于执行本发明实施例提供的任意一项方法流程；
所述网关设备，用于依据所述连接类型对所述用户设备进行服务质量控制或者计费控制。
在一个可能的实现方式中，所述网络系统还包括策略控制功能设备、会话管理设备或用户面功能设备；
所述移动管理设备，还用于向所述策略控制功能设备、所述会话管理设备或所述用户面功能设备发送所述连接类型；
所述策略控制功能设备，用于依据所述连接类型对所述用户设备下发服务质量策略或计费控制策略；或者，
所述会话管理设备，用于依据所述连接类型对所述用户设备进行服务质量控制或者计费控制；或者，
所述用户面功能设备，用于依据所述连接类型对所述用户设备进行服务质量控制或者计费控制。
第四方面，本发明实施例还提供了一种移动管理设备，包括：
识别单元，用于识别用户设备通过接入节点设备接入核心网所采用的连接类型，所述连接类型为单连接或双连接；在所述连接类型为单连接的情况下，所述用户设备通过1个接入节点设备接入所述核心网；在所述连接类型为双连接的情况下，所述用户设备通过两个接入节点设备接入所述核心网；
接入控制单元，用于依据所述用户设备的连接类型，对所述用户设备进行接入控制。
在一个可能的实现方式中，所述识别单元，用于根据接入节点设备发送的所述用户设备的接入类型参数，确定所述用户设备的连接类型，所述接入类型参数用于指示所述用户设备的无线接入类型或所述接入节点设备的类型；
或者，根据所述用户设备的双连接能力、所述用户设备的签约信息以及所述移动管理设备的本地配置中的一项或多项，确定所述用户设备的连接类型；
或者，接收所述接入节点设备发送的数据使用报告，所述数据使用报告中包含用户设备的流量信息，所述移动管理设备根据所述数据使用报告确定所述用户设备的连接类型；
或者，接收携带所述接入节点设备的互联网协议IP地址的消息，根据所述接入节点设备的IP地址确定所述用户设备的连接类型。
在一个可能的实现方式中，所述识别单元，用于根据接入节点设备发送的所述用户设备的接入类型参数，确定所述用户设备的连接类型包括：根据接入节点设备发送的无线接入承载更新请求消息，或通道切换请求消息，或业务流的通知消息中包含的接入类型参数，确定所述用户设备的连接类型。
在一个可能的实现方式中，所述识别单元，用于接收携带所述接入节点设备的互联网协议IP地址的消息，根据所述接入节点设备的IP地址确定所述用户设备的连接类型包括：
接收初始上下文建立响应消息，分组数据单元PDU会话资源建立响应消息或者缺省承载建立响应消息，在所述初始上下文建立响应消息，PDU会话资源建立响应消息或者缺省承载建立响应消息中携带所述接入节点设备的IP地址；根据所述接入节点设备的IP地址确定所述用户设备的连接类型。
在一个可能的实现方式中，所述识别单元，用于根据所述用户设备的双连接能力、所 述用户设备的签约信息以及所述移动管理设备的本地配置的一项或多项，确定所述用户设备的连接类型包括：
用于根据所述用户设备发送的所述用户设备的双连接能力的信息，确定所述用户设备的连接类型，或者，
用于根据从所述用户设备的归属用户服务器获取所述用户设备的签约信息，确定所述用户设备的连接类型，或者，
用于根据所述移动管理设备的本地配置中包含的是否允许所述用户设备建立双连接的信息，确定所述用户设备的连接类型。
在一个可能的实现方式中，所述识别单元，用于接收所述接入节点设备发送的数据使用报告，所述数据使用报告中包含用户设备的流量信息，所述移动管理设备根据所述数据使用报告确定所述用户设备的连接类型包括：用于确定在所述用户设备的连接态周期内，接收到接入节点设备发送的数据使用报告，则确定所述用户设备的连接类型为双连接。另一方面，如果确定在所述用户设备的连接态周期内，没有接收到所述接入节点设备发送的数据使用报告，则确定所述用户设备的连接类型为单连接。
在一个可能的实现方式中，所述移动管理设备还包括：
标记单元，用于根据接收的接入节点设备的IP地址，将接入节点设备区分为第一基站或第二基站；
所述识别单元，具体用于在所述用户设备接入的接入节点设备包含第一基站和第二基站时，所述移动管理设备确定所述用户设备的连接类型为双连接；在所述用户设备接入的接入节点设备只包含第一基站时，所述移动管理设备确定所述用户设备的连接类型为单连接。
在一个可能的实现方式中，所述标记单元，用于在所述用户设备不被允许建立双连接的情况下，所述移动管理设备在接收到所述接入节点设备的IP地址后，将所述接入节点设备的IP地址对应的接入节点设备标记为第一基站；获取业务数据包的转发通道建立到第一基站的流程中接收的接入节点设备的IP地址，将所述接入节点设备的IP地址对应的接入节点设备标记为第一基站；在所述用户设备接入两个IP地址，且其中一个IP地址对应的接入节点设备为第一基站时，将所述两个IP地址中的另一IP地址对应的接入节点设备标记为第二基站。
在一个可能的实现方式中，所述业务数据包的转发通道建立到第一基站的流程包括：注册流程、跟踪区域更新、服务请求流程以及附着流程中的任意一项。
在一个可能的实现方式中，所述移动管理设备还包括：
记录控制单元，用于在所述标记单元标记IP地址对应的接入节点设备为第一基站或第二基站后的预定时间之后，删除标记的IP地址对应的接入节点设备为第一基站或第二基站的信息。
在一个可能的实现方式中，所述移动管理设备还包括：
发送单元，用于向网关设备发送识别的所述连接类型。
第五方面，本发明实施例还提供了一种对用户设备进行接入控制的方法，包括：
策略控制功能设备接收移动管理设备发送的用户设备的连接类型；
所述策略控制功能设备依据所述连接类型对所述用户设备下发服务质量策略或计费控制策略。
第六方面，本发明实施例还提供了一种对用户设备进行接入控制的方法，包括：
会话管理设备接收移动管理设备发送的用户设备的连接类型；
所述会话管理设备依据所述连接类型对所述用户设备进行服务质量控制或者计费控制。
第七方面，本发明实施例还提供了一种对用户设备进行接入控制的方法，包括：
用户面功能设备接收移动管理设备发送的用户设备的连接类型；
所述用户面功能设备依据所述连接类型对所述用户设备进行服务质量控制或者计费控制。
第八方面，本发明实施例还提供了一种网络设备，该网络设备可以是移动管理设备、网关设备、策略控制功能设备、会话管理设备以及用户面功能设备中的任意一种，包括：处理器、存储器和收发器；所述述处理器、所述存储器和所述收发器以可通信方式连接；
在所述存储器中存储有程序代码；
所述处理器用于读取所述程序代码与所述收发器配合实现本发明实施例中由移动管理设备实现的方法的功能。
第九方面，本发明实施例还提供了一种计算机存储介质，
所述存储介质中存储有程序代码，所述程序代码包括程序指令，所述程序指令当被处理器执行时使所述处理器与收发器配合实现本发明实施例任意一项方法的功能。
第十方面，本发明实施例还提供了一种计算机程序产品，在上述计算机程序产品中包含程序指令，上述程序指令当被上述处理器执行时使处理器与收发器配合实现本发明实施例中由移动管理设备、网关设备、策略控制功能设备、会话管理设备以及用户面功能设备中的任意一种实现的任意一项方法的功能。
在以上所有方面提供的技术方案中，移动管理设备可以为移动管理实体，也可以为接入管理功能设备。
在以上所有方面提供的技术方案中，网关设备可以为数据网关，也可以为服务网关或会话管理功能设备、用户面功能设备、计费设备。
以上所有方面提供的技术方案中，网关设备、策略控制功能设备、会话管理设备以及用户面功能设备所使用的用户设备的接入类型可以来自于移动管理设备所确定的接入类型，用户设备的接入类型的识别方式可以参考第一方面的实施例。
附图说明
为了更清楚地说明本发明实施例或背景技术中的技术方案，下面将对本发明实施例或背景技术中所需要使用的附图进行说明。
图1A-图1E为本发明实施例混合组网的网络架构图；
图2为本发明实施例5G网络的网络架构图；
图3为本发明实施例方法流程示意图；
图4为本发明实施例方法流程示意图；
图5为本发明实施例方法流程示意图；
图6为本发明实施例方法流程示意图；
图7为本发明实施例方法流程示意图；
图8为本发明实施例网络系统结构示意图；
图9为本发明实施例移动管理设备结构示意图；
图10为本发明实施例网络设备结构示意图。
具体实施方式
下面结合本发明实施例中的附图对本发明实施例进行描述。
如图1A-图1E，为5种混合组网架构的示意图，这些混合组网架构混合了4G接入网和5G接入网。其中，图1A-图1C、1E所述的架构可以称为非独立组网架构。
在上述混合组网架构中，用户设备同时与两个接入节点设备(后面简称接入节点或节点设备)建立连接，分别为接入节点1和接入节点2；用户设备的业务数据可以通过这两个接入节点中的任意一个或两个进行转发。在非独立组网架构中，用户设备也可以仅与一个接入节点建立连接。
其中，在图1A的模式下(option 3模式)，网络侧的服务网关将业务数据包发送给接入节点1，由接入节点1根据用户设备的双连接能力，以及网络状态等将部分业务数据包分流到接入节点2转发给用户设备。在本发明实施例中业务数据使用数据包形式转发，因此可以将业务数据称为业务数据包，后续实施例中不再一一说明。在图1A、图1B以及图1C中所示的服务网关属于网关设备的一种，在后续实施例中还会提到其他的网关设备，例如：数据网关、SMF设备、UPF设备等。
在图1B的模式下(option 3a模式)，业务数据包在服务网关处分流到接入节点1和接入节点2，再由接入节点1和接入节点2分别将接收到的业务数据包转发给用户设备。
在图1C的模式下(option 3x模式)，网络侧将业务数据包发送给接入节点2，接入节点2可将部分业务数据包分流到接入节点1，接入节点1将收到的业务数据包转发给用户设备，接入节点2将未分流到接入节点1的业务数据包转发给用户设备。
在图1A、图1B以及图1C所示的非独立组网架构中，将和移动管理设备有信令接口的接入节点1称为主接入节点、第一接入节点或主接入节点设备，将和移动管理设备没有信令接口的接入节点2称为辅接入节点、第二接入节点或辅接入节点设备。
图1A、图1B以及图1C所示的非独立组网架构的示意图，可以应用在演进的分组系统(evolved packet system，EPS)网络。接入节点1和接入节点2是用户设备接入到核心网的节点，其中，主接入节点可以是基站(例如NodeB)，辅接入节点可以是演进型基站(evolved NodeB，eNB)、5G移动通信系统中的下一代基站(next generation NodeB，gNB)或未来移动通信系统中的基站等。移动管理设备可以是MME，服务网关可以是服务网关(serving gateway，S-GW)，数据网关可以是分组数据网络网关(packet data network gateway，PDN-GW)。
在图1D所示的组网架构图中，接入节点1和接入节点2连接到5G核心网(5G Core，5GC)中，用户设备可以同时连接接入节点1和接入节点2。其中，接入节点1可以为支 持演进LTE(evolved LTE，eLTE)接入的eNB，接入节点2可以为支持NR接入的gNB。控制面的信令通过gNB传输给5GC，即信令锚定点在gNB。上述组网架构可以对应于option4组网方式。此外，eNB也可以不通过gNB,而直接与5GC连接，这种情况下对应于option 4a组网方式。
在图1E所示的组网架构图中，接入节点1和接入节点2连接到5G核心网(5G Core，5GC)中，用户设备可以同时连接接入节点1和接入节点2。其中，接入节点1可以为支持演进LTE(evolved LTE，eLTE)接入的eNB，接入节点2可以为支持NR接入的gNB。控制面的信令通过eNB传输给5GC，即信令锚定点在eNB。上述组网架构可以对应于option7组网方式。gNB也可以不通过eNB,而直接与5GC连接，这种情况下对应于option7a/7x组网方式。
图1A-图1E所示的组网架构的示意图，可以应用到5G网络；如图2所示的5G网络架构示意图，包括：用户设备、无线网络和5G核心网；用户设备通过当前位置的接入节点接入无线网络，核心网设备用于用户设备的注册、安全认证、移动性管理、位置管理、会话管理和转发用户设备和外部数据网络之间的数据包等。
其中，图2中无线网络包含的设备可以为新空口(new radio，NR)设备；核心网设备包含会话管理功能(session management function，SMF)设备，AMF设备，用户面功能(user plane function，UPF)设备，统一数据管理(unified data management，UDM)设备，策略控制功能(policy control function，PCF)设备，鉴权服务功能(authentication server function，AUSF)设备，网络切片选择功能(network slice selection function，NSSF)设备，网络公开功能(network exposure function，NEF)设备，网络仓库功能(network repository function，NRF)设备和应用功能(application function，AF)设备等，本申请实施例对此不作具体限定。
其中，NR设备可以对应到图1A至图1C中的接入节点，接入和移动性管理功能AMF可以对应到图1A-图1C中的移动管理设备。另外，在图2中所示的N1、N2、N3、N4、N9、N6、Nnssf、Nnef、Nnrf、Nnpcf、Nudm、Naf、Nausf、Namf以及Nsmf均为服务化接口，在此不再赘述。
在图1D-图1E所示的组网场景下，双连接的用户设备与两个接入节点建立连接，此时用户设备连接两个5G基站，也即：主接入节点和辅接入节点均为5G基站。针对图2所示的5G网络架构，主接入节点可以是eNB，辅接入节点可以是gNB，或者主接入节点可以是下一代基站gNB，辅接入节点可以是演进型基站eNB。
如图1A-图1E以及图2所示网络架构，本发明实施例提供了识别用户设备的接入类型的方法，在识别用户设备的接入类型后可以执行接入控制，具体可以包括：移动管理设备识别用户设备通过接入节点设备接入核心网所采用的连接类型，所述连接类型为单连接或双连接；在所述连接类型为单连接的情况下，所述用户设备通过1个接入节点设备接入所述核心网；在所述连接类型为双连接的情况下，所述用户设备通过两个接入节点设备接入所述核心网；
所述移动管理设备依据所述用户设备的连接类型，对所述用户设备进行接入控制。后续实施例中，将分别就不同的网络架构下，移动管理设备识别用户设备的连接类型的方法， 以及识别后的使用进行举例说明。其中，识别后的使用可以包括对用户设备进行接入限制、计费策略，服务质量控制策略和许可(license)控制等。
移动管理设备识别用户设备的连接类型的第一类方法举例：
主接入节点主动通知移动管理设备用户设备的接入类型，该接入类型可以为接入节点类型或者无线接入类型等，移动管理设备根据该接入类型获知用户设备的业务数据包经过主接入节点还是辅接入节点转发，由此获知所述用户设备属于单连接用户设备或双连接用户设备。
下面给出具体的实施例来描述本申请中移动管理设备确定用户的连接类型的方案。以用户设备接入4G核心网EPS为例，结合图2所示的5G网络，本实施例可以适用于图1A-图1C的组网架构。
在本实施例的非独立组网架构中，用户设备双连接的建立由主接入节点决策，对于双连接用户设备而言，主接入节点可能触发辅接入节点的添加、更新以及删除等流程，这些流程用于建立、更新以及删除通过辅接入节点的业务数据包的转发通道。
例如：
当主接入节点决定将用户设备的某个承载的业务数据包由辅接入节点转发时，主接入节点触发辅接入节点添加流程，为用户设备建立双连接；或者，
当用户设备已经建立了双连接，主接入节点决定将用户设备的某个承载的业务数据包由主接入节点改为辅接入节点转发时，主接入节点触发辅接入节点的更新流程，将该承载切换到辅接入节点；或者，
当用户设备已经建立了双连接，主接入节点决定将用户设备的由辅接入节点转发的业务数据包改为由主接入节点转发时，主接入节点触发辅接入节点删除流程。
在以上三种流程中，由于涉及到承载的业务数据包由主接入节点转发改为由辅接入节点转发，或者由辅接入节点转发改为由主接入节点，主接入节点可以通知网络侧主接入节点或者辅接入节点的用于接收业务数据包的IP地址和TEID，基于此本发明实施例流程可以具体为：
301：主接入节点发送演进通用陆地无线接入网无线接入承载(evolved universal terrestrial radio access network radio access bearer，E-RAB)更新指示消息给移动管理设备，该E-RAB更新指示消息中携带主接入节点或辅接入节点的IP地址和TEID，用于通知网络修改下行数据包的转发通道。
其中，该E-RAB更新指示消息中还可以携带接入类型参数，该接入类型参数可以为接入节点类型，如NodeB，eNB或gNB等，所述接入类型参数也可以为无线接入类型，如演进通用陆地无线接入(evolved universal terrestrial radio access，E-UTRA)或者NR等。其中，转发业务数据包的接入节点类型为NodeB或者eNB时，对应的无线接入类型为E-UTRA。转发业务数据包的接入节点类型为gNB时，对应的无线接入类型为NR。
移动管理设备收到上述无线接入承载更新请求消息后，根据其中携带的接入类型参数和当前的组网模式，获知这个承载对应的业务数据包由主接入节点还是辅接入节点转发。
更具体地，如果接入类型参数为eNB或gNB或NR，则移动管理设备获知转发业务数 据包的接入节点为辅接入节点。如果接入类型参数为NodeB或E-UTRA，则移动管理设备获知转发业务数据包的接入节点为主接入节点。如果用户设备有任意一个承载对应的业务数据包由辅接入节点转发，则移动管理设备确定用户设备为双连接用户设备；如果用户设备所有承载对应的业务数据包都由主接入节点转发，则移动管理设备确定上述用户设备为单连接用户设备。
移动管理设备基于用户设备是双连接用户设备或单连接用户设备的信息，可以进行对用户设备的接入控制，具体的接入控制例如：
移动管理设备基于用户设备的双连接能力，以及签约数据中的双连接能力，对有双连接能力但是当前为单连接的用户进行接入控制，用户设备将不能正常使用数据业务；或者，
对单连接用户设备或双连接用户设备分别进行License控制，即区分统计单连接用户设备数，和双连接用户设备数，当单连接用户设备数或者双连接用户设备数超过License购买的值时，移动管理设备进行告警或者限制新的用户设备接入。
302：移动管理设备发送更新承载请求(modify bearer request)消息给服务网关，在该更新承载请求消息中携带主接入节点或辅接入节点的IP地址和TEID，所述无线接入承载更新请求消息中还携带上述接入类型参数。
服务网关在接收到上述更新承载请求消息后，存储其中携带的接入节点的IP地址和TEID。后续所述承载对应的业务数据包，服务网关将发送给上述IP地址和TEID对应的接入节点。
服务网关可以参考移动管理设备根据接入类型参数确定用户设备为单连接用户设备或双连接用户设备的方式，在此不再赘述。
服务网关基于用户设备为单连接用户设备或双连接用户设备的信息，可以对单连接用户设备或者双连接用户设备进行区分计费。甚至对于同一用户设备，可以对于主接入节点转发的业务数据包，和对于辅接入节点转发的业务数据包，进行区分计费。例如，辅接入节点转发的业务数据包的费率低于通过主接入节点转发的业务数据包的费率。
进一步地，服务网关可以将上述承载对应的接入类型参数发送给数据网关，数据网关可以将用户设备的连接类型通知给策略控制功能，以便对单连接用户设备或者双连接用户设备进行不同的服务质量控制或者计费控制。
303：服务网关回复更新承载响应(modify bearer response)消息给移动管理设备，用于通知所述承载的下行通道更新完成。
304：移动管理设备回复E-RAB更新指示确认(E-RAB modification indication confirm)给主接入节点，通知所述承载的下行通道更新完成。
后面的双连接切换流程简单补充一下，便于方案的完整。
以上流程以主接入节点执行建立、更新以及删除通过辅接入节点传输业务数据包的转发通道的流程为例，使用E-RAB更新指示消息携带接入类型参数给移动管理设备；另外，主接入节点还可以在其他流程使用其他消息将接入类型参数发送给移动管理设备，例如：在终端进行X2切换流程中，主接入节点采用通道切换请求消息通知主接入节点/辅接入节点的IP地址和TEID，在该通道切换请求消息中携带上述接入类型参数，使得移动管理设备及网络中的其他设备可以根据接入类型参数来确定用户设备为单连接用户设备或者双 连接用户设备。
以用户设备接入5G核心网为例，如图4所示，本实施例可以适用于图1D和图1E的组网架构，请一并参考图2所示的5G网络架构。
本实施例中，主接入节点以服务质量流(quality of service flow,QoS Flow)的粒度来分流业务数据包，主接入节点将服务质量流(简称业务流)对应的主接入节点或辅接入节点的IP地址和TEID通知给AMF或SMF，以便AMF或SMF确定用户设备的连接类型，并根据连接类型对用户设备进行不同的策略控制。
在本实施例的非独立组网架构中，用户设备的双连接的建立由主接入节点决策，对于双连接用户设备，主接入节点可能触发辅接入节点添加、更新以及删除等流程，用于建立、更新以及删除通过辅接入节点的业务数据包的转发通道。
例如：
当主接入节点决定将用户设备的某个业务流(QoS Flow)的业务数据包由辅接入节点转发时，主接入节点触发辅接入节点添加流程，为用户设备建立双连接；或者，
当用户设备已经建立了双连接，主接入节点决定将用户设备的某个业务流的业务数据包改由辅接入节点转发时，主接入节点触发辅接入节点的更新流程，将该业务流切换到辅接入节点；或者，
当用户设备已经建立了双连接，主接入节点决定将由辅接入节点转发的用户设备的业务数据包改为由主接入节点转发时，主接入节点触发辅接入节点的删除流程。
在以上三种流程中，因为涉及到业务流的业务数据包由主接入节点转发改为由辅接入节点转发，或者由辅接入节点转发改为由主接入节点转发，主接入节点需要通知网络侧主接入节点或者辅接入节点的连接信息(例如用于接收业务数据包IP地址和TEID)，基于此本发明实施例流程可以具体为：
401：主接入节点发送PDU会话资源更新指示(session resource update indication)消息给接入和移动性管理功能，该PDU会话资源更新指示消息中携带主接入节点或辅接入节点的IP地址和TEID，用于通知接入和移动性管理功能修改下行数据包的转发通道。
其中，该PDU会话资源更新指示消息中还携带接入类型参数，该接入类型参数可以为接入节点类型，如eNB或gNB等，所述接入类型参数也可以为无线连接类型，如E-UTRA或者NR等。转发业务数据包的接入节点为eNB时，无线连接类型为E-UTRA，转发业务数据包的接入节点为gNB时，无线连接类型为NR。
接入和移动性管理功能收到PDU会话资源更新指示消息后，根据接入类型参数和组网模式，获知上述业务流的业务数据包由主接入节点还是辅接入节点转发。如果用户设备有任意一个业务流的业务数据包由辅接入节点转发，则接入和移动性管理功能确定该用户设备为双连接用户设备；如果用户设备所有业务流的业务数据包都由主接入节点转发，则接入和移动性管理功能确定该用户设备为单连接用户设备。
接入和移动性管理功能可以基于上述用户设备是单连接用户设备或双连接用户设备的信息，对上述用户设备进行接入控制，如：
基于用户设备的双连接能力，签约数据中的双连接能力，对有双连接能力但是当前为 单连接的用户设备进行接入控制，使该用户设备将不能正常使用数据业务；或者，
对单连接用户设备或双连接用户设备分别进行License控制，即区分统计单连接用户设备数和双连接用户设备数，当单连接用户设备数或者双连接用户设备数超过License购买的值时，移动管理设备进行告警或者限制新的用户设备接入。
402：接入和移动性管理功能发送PDU会话上下文更新请求(PDU session updatecontextrequest)消息给会话管理功能。
其中，该PDU会话上下文更新请求消息中携带主接入节点或辅接入节点的IP地址和TEID，所述PDU会话上下文更新请求消息中还携带接入类型参数。该PDU会话上下文更新请求可以通过Nsmf接口发送。
会话管理功能可以参考接入和移动性管理功能根据接入类型参数确定用户设备是单连接用户设备或双连接用户设备的方式，在此不再赘述。
会话管理功能基于上述用户设备是单连接用户设备或双连接用户设备的信息，可以对单连接用户设备或者双连接用户设备进行区分的计费或者服务质量控制，甚至对于同一用户设备，可以对于主接入节点转发的业务数据包，和对于辅接入节点转发的业务数据包，进行区分计费或者服务质量控制。
进一步，会话管理功能可以将上述业务流对应的接入类型参数通知给策略控制功能，以便策略控制功能对单连接用户设备或者双连接用户设备进行不同的服务质量控制或者计费控制等。
403：会话管理功能发送N4会话更新请求(session modification request)消息给用户面功能，该N4会话更新请求消息中携带主接入节点或辅接入节点的IP地址和TEID，该N4会话更新请求消息中还携带接入类型参数，以便用户面功能对单连接用户设备或者双连接用户设备进行不同的服务质量控制或者计费控制。
用户面功能存储上述N4会话更新请求消息中携带的IP地址和TEID，后续上述用户设备的业务流的业务数据包，用户面功能将发送给上述IP地址和TEID对应的接入节点。
404：用户面功能回复N4PDU会话更新响应(session modification response)消息给会话管理功能。该PDU会话更新响应可以在Nsmf接口发送。
405：会话管理功能回复PDU会话上下文更新响应(PDU session update context response)消息给接入和移动性管理功能，用于通知上述业务流的下行通道更新完成。
406：接入和移动性管理功能回复PDU会话资源更新确认(PDU session resource update acknowledge)消息给上述主接入节点，通知上述业务流的下行通道更新完成。
以上流程以主接入节点执行建立、更新以及删除通过辅接入节点的业务数据包的转发通道的流程为例，使用PDU会话资源更新指示消息携带接入类型参数给接入和移动性管理功能；另外，主接入节点还可以在UE进行X2切换流程中，采用通道切换请求消息通知主接入节点/辅接入节点的IP地址和TEID时，在该通道切换请求消息中携带接入类型参数，使得接入和移动性管理功能及网络中的其他设备据此确定用户设备为单连接用户设备或者双连接用户设备。
以上给出了移动管理设备根据接入类型参数来识别用户设备的连接类型的方案，下面 再给出移动管理设备识别用户设备的连接类型的另一种方案。在该方案中，核心网的设备，例如移动管理设备(MME或AMF)可以通过自学习获知用户设备为单连接用户设备或双连接用户设备。
以用户设备通过无线接入网接入EPS核心网为例，如图5所示，其中，归属用户服务器(home subscriber server，HSS)负责用户签约信息的管理和维护。归属用户服务器也可以融合UDM的功能。
501：用户设备开机，发起附着流程，发送附着请求消息给移动管理设备，该附着请求消息经过主接入节点转发给移动管理设备。
其中，所述附着请求消息中携带上述用户设备的双连接能力的信息，如用户设备支持与新空口的双连接(dual connectivity with NR)能力。
502:移动管理设备向上述用户设备的HSS发送签约数据获取请求。
503：移动管理设备接收上述HSS返回的签约数据获取响应，在该签约数据获取响应中包含上述用户设备的签约数据，该签约数据中包含用户设备的双连接能力的信息。
例如：签约数据中包括新空口辅助无线接入类型(NR as secondary radio access type，NR as secondary RAT)能力。
其中，移动管理设备通过自学习识别用户设备的连接类型可以通过如下方式：
移动管理设备根据用户设备发送的双连接能力信息和签约数据中的双连接能力信息，对于有双连接能力且签约数据中签约了双连接能力的用户设备识别为双连接用户设备。
此外，移动管理设备还可以结合本地配置识别用户设备，例如将本地配置允许建立双连接的用户设备识别为双连接用户设备。将本地配置不允许建立双连接的用户设备识别为单连接用户设备。
移动管理设备基于识别的双连接用户设备或单连接用户设备的信息，可以对用户设备进行接入控制，如：
对单连接用户设备或双连接用户设备分别进行License控制,即区分统计单连接用户设备数，和双连接用户设备数，当单连接用户设备数或者双连接用户设备数超过License购买的值时，移动管理设备进行告警或者限制新的用户设备接入。
504：移动管理设备发送建立会话请求消息给服务网关；
对于双连接用户设备，该建立会话请求消息中携带双连接能力指示，如与新空口的双连接(dual connectivity with NR)能力；
服务网关对于携带双连接能力指示的用户设备，可以识别为双连接用户设备。
服务网关基于上述用户设备是否属于双连接用户设备的信息，可以对单连接用户设备或者双连接用户设备进行区分计费。
505：服务网关SGW发送建立会话请求消息给数据网关；
对于双连接用户设备，该建立会话请求消息中携带双连接能力指示，如dual connectivity with NR能力。
数据网关PGW对于携带双连接能力指示的用户设备，识别为双连接用户设备。
数据网关基于上述用户设备是否属于双连接用户设备的信息，可以对单连接用户设备或者双连接用户设备进行区分的计费或服务质量控制。
数据网关还可以将所述双连接能力指示发送给策略控制功能，以便策略控制功能对单连接用户设备或者双连接用户设备进行不同的服务质量控制或者计费控制。
506：数据网关回复建立会话响应消息给服务网关，回复服务网关和数据网关之间的会话建立成功。
507：服务网关回复建立会话响应消息给移动管理设备，回复服务网关和移动管理设备之间的会话建立成功。
508：移动管理设备发送附着接受消息给用户设备，完成用户设备的附着流程。
509：移动管理设备发送更新承载请求(modify bearer request)消息给服务网关，通知服务网关建立业务数据包转发的下行隧道。
在本步骤中，具体流程可以是：移动管理设备发送更新承载请求消息给服务网关，在该更新承载请求消息中携带主接入节点或辅接入节点的IP地址和TEID；服务网关在接收到上述更新承载请求消息后，存储其中携带的接入节点的IP地址和TEID。服务网关将上述承载对应的业务数据包，发送给上述IP地址和TEID对应的接入节点。
510：服务网关回复更新承载响应(modify bearer response)消息给移动管理设备，用于通知上述承载的下行通道更新完成。
以上实施例以附着流程为例进行了介绍，UE在进行跟踪区域更新时，核心网中的设备也可以识别用户设备的连接类型。此时，UE在跟踪区更新请求消息中携带上述双连接能力指示，移动管理设备接收到跟踪区更新请求消息后，采用上面类似的自学习方法识别用户设备的连接类型。随后，移动管理设备还可以发送建立会话请求消息给服务网关，其中携带用户设备的双连接能力指示。移动管理设备、服务网关和数据网关的处理流程和附着流程类似，本实施例不再赘述。
仍以用户设备通过无线接入网接入EPS核心网为例，如图6所示，本实施例的非独立组网架构下，主接入节点可以触发双连接用户设备的流量上报流程，将通过辅接入节点转发的承载以及对应的转发流量信息通知给包括移动管理设备在内的核心网设备。
601，主接入节点发送用户设备的流量使用报告(secondary rat usage data report)消息给移动管理设备，该流量使用报告消息中携带承载标识，以及对应的流量信息。
如果流量使用报告中包含辅接入节点转发的流量信息，则移动管理设备根据确定该用户设备为双连接用户设备。如果流量使用报告中只有主接入节点转发的流量信息，则移动管理设备根据确定该用户设备为单连接用户设备。其中，用户设备的流量信息包括用户设备的上下行数据包的流量信息。
移动管理设备可以对该用户设备进行接入控制，如：
基于用户的双连接能力，签约数据中的双连接能力，对有双连接能力但是当前为单连接的用户进行接入控制，用户设备将不能正常使用数据业务；
对单连接用户设备或双连接用户设备分别进行License控制，即区分统计单连接用户设备数，和双连接用户设备数，当单连接用户设备数或者双连接用户设备数超过License购买的值时，移动管理设备进行告警或者限制新的用户设备接入。
602：移动管理设备发送流量上报通知消息给服务网关。
服务网关可以参考移动管理设备依据流量上报通知消息确定上述用户设备属于单连接用户设备或双连接用户设备的方式。
服务网关基于上述用户设备属于单连接用户设备或双连接用的信息，可以对单连接用户设备或者双连接用户设备进行区分计费；对于同一用户设备，还可以对主接入节点转发的业务数据包，和辅接入节点转发的业务数据包，进行区分计费。
603：服务网关发送上述流量上报通知消息给数据网关。
数据网关可以参考接入和移动性管理设备根据流量上报通知消息确定用户设备是单连接用户设备或双连接用户设备的方式，在此不再赘述。
数据网关基于上述用户设备属于单连接用户设备或双连接用户设备的信息，可以对单连接用户设备或者双连接用户设备进行区分的计费或者服务质量控制。
数据网关还可以将流量上报通知消息发送给策略控制功能，以便策略控制功能对单连接用户设备或者双连接用户设备进行不同的服务质量控制或者计费控制等。
604：数据网关回复改变通知确认(change notification ACK)消息；
605：服务网关回复改变通知确认消息。
在本实施例中，上述流量上报通知消息可以通过专有流程上报，也可以在当前流程的信令消息中上报，并不影响本实施例的实现，在此不再赘述。上述当前流程可以是：切换，注册更新，服务请求，PDU会话更新/删除，跟踪区域更新，专有承载更新/删除等流程。
另外，移动管理设备在用户设备的连接态周期内收到主接入节点上报的流量使用报告，则移动管理设备在S1释放(release)流程后仍然将上述用户设备标记为双连接用户设备。如果移动管理设备在连接态周期内没有收到主接入节点上报的流量使用报告，则S1release流程后将所述用户设备标记为单连接用户设备。本实施例，在已经获知用户设备的连接类型后，可以通过主接入节点在连接态周期内是否有上报流量使用报告来确定用户的连接类型，不用额外消耗信令，也不用传递额外的数据，节省了网络的资源。
以用户设备接入5G核心网为例，如图7所示，在本实施例，主接入节点可以触发双连接用户设备的流量上报流程，主接入节点将通过辅接入节点转发的业务流以及流量上报通知给包括接入和移动性管理功能在内的核心网设备。
701：主接入节点发送流量使用报告(secondary rat usage data report)消息给接入和移动性管理功能，所述流量上报通知消息中携带业务流标识(QoS flowID,QFI)，以及对应的流量信息。
接入和移动性管理功能根据上述流量上报通知消息，确定该用户设备为双连接用户设备，可以对用户设备进行接入控制，如：
对单连接用户设备或双连接用户设备分别进行License控制，即区分统计单连接用户设备数，和双连接用户设备数，当单连接用户设备数或者双连接用户设备数超过License购买的值时，接入和移动性管理功能进行告警或者限制新的用户设备接入。
702：接入和移动性管理功能发送PDU会话上下文更新请求(PDU session_updatecontextrequest)给会话管理功能，上述流量上报通知消息中携带701 中获得的业务流标识，及其对应的流量信息。
其中，该PDU更新会话管理上下文请求使用Nsmf接口发送。
会话管理功能可以参考接入和移动性管理功能依据流量上报通知消息确定用户设备属于单连接用户设备或双连接用户设备的方式，在此不再赘述。
会话管理功能基于上述用户设备为单连接用户设备或双连接用户设备的信息，可以对单连接用户设备或者双连接用户设备进行区分的计费和服务质量控制；另外，针对同一用户设备，可以对于主接入节点转发的业务数据包，和对于辅接入节点转发的业务数据包，进行区分计费和服务质量控制。
703：会话管理设备PDU会话上下文更新响应(PDU session_update context response)。
其中，该PDU更新会话管理上下文响应可以使用Nsmf接口发送。
在本实施例中，上述流量上报可以通过列举的专有流程上报，也可以在当前流程的信令消息中上报，并不影响本实施例的实现，在此不再赘述。上述专有流程是指专门下发change notification request的流程；上述当前流程可以是：切换，注册更新，服务请求，PDU会话更新/删除，跟踪区域更新，专有承载更新/删除等流程。
另外，接入和移动性管理功能在用户设备的连接态周期内收到主接入节点上报的Secondary RAT Usage Data Report，则接入和移动性管理功能在N2释放(release)流程后将上述用户设备标记为双连接用户设备。如果接入和移动性管理功能在连接态周期内没有收到主接入节点上报的Secondary RAT Usage Data Report，则N2 Release流程后将上述用户设备标记为单连接用户设备。
本发明实施例还提供了网络侧设备自学习标记接入节点类型，并据此确定用户设备的连接类型的方法，具体如下：
一、以EPS为例：
在以上图3和图5所示的流程中，主接入节点在发送为承载分配的IP地址和TEID给移动管理设备后，移动管理设备转发给服务网关。移动管理设备可以首先对IP地址对应的接入节点进行标记，具体如下：
1、移动管理设备在确认是否可以允许用户设备使用双连接后，对于不允许使用双连接的用户设备，即单连接用户设备，移动管理设备收到的接入节点的IP地址和TEID应当是主接入节点分配的，因此移动管理设备可以将此IP地址对应的接入节点标记为主接入节点或第一基站。
2、移动管理设备在确认允许用户设备使用双连接，在前文举例的跟踪区域更新、服务请求流程以及附着等特定流程中，主接入节点将承载的业务数据包的转发通道先建立到主接入节点上，即发送给移动管理设备的接入节点的IP地址和TEID应当为主接入节点分配的。因此移动管理设备在这些特定流程中，收到接入节点的IP地址和TEID后，则将收到的IP地址对应的接入节点标记为第一基站；或者更具体地标记为：4G基站，eNodeB，主接入节点或者第一接入节点。即，移动管理设备收到接入节点发送的初始上下文响应消息，获取消息中携带的接入节点的IP地址和TEID后，将此将此IP地址对应的接入节点标记为第一基站。
3、移动管理设备在确认用户设备的连接类型为双连接用户设备后，收到新的接入节点的IP地址则可以标记为第二基站，或者更具体地标记为：5G基站，gNB或者，eNB，或者辅接入节点。或者，如果移动管理设备收到多个接入节点的IP地址，则将同一个用户设备的，不同于标记为第一基站的用户面IP地址对应的接入节点标记为第二基站。
例如：图3所示，由于E-RAB指示消息是为双连接用户设备发送的，移动管理设备收到E-RAB更新指示消息后，在该E-RAB更新指示消息中携带接入节点的IP地址和TEID。由于已经有被标记为第一基站的IP地址，而当前E-RAB更新指示消息中携带的接入节点的IP地址不同于上述已经标记的第一基站的IP地址，因此移动管理设备将新收到的E-RAB更新指示消息中的IP地址对应的接入节点标记为第二基站。
进一步的，移动管理设备通过以上3个方法标记了基站类型，该移动管理设备可以为此设置老化定时器，老化定时器超时后，将标记的基站类型清空，重新执行本实施例的学习过程。
基于上述的自学习过程，移动管理设备可以获知用户设备建立的承载，哪些是建立在主接入节点上，哪些是建立在辅接入节点上。据此，移动管理设备可以识别用户设备的连接类型，具体为：当用户设备有任意一个承载建立在辅接入节点时，移动管理设备确定该用户设备为双连接用户设备；当用户设备所有承载都建立在主接入节点时，移动管理设备确定该用户设备为单连接用户设备。
进一步的，移动管理设备在通过自学习识别用户设备的接入点类型得到识别结果后，可以将该识别结果通知给服务网关、数据网关以及策略控制功能等设备，比如将识别的接入点类型发给服务网关、数据网关以及策略控制功能。又比如，通过信令消息将用户设备为单连接用户设备或者双连接用户设备的信息通知给服务网关、数据网关以及策略控制功能等设备。
二、以5G核心网为例：
在以上图4所示的流程中，主接入节点在发送为承载分配的IP地址和TEID给接入和移动性管理功能后，接入和移动性管理功能转发给会话管理功能，会话管理功能转发给用户面功能。接入和移动性管理功能可以首先对IP地址对应的接入节点进行标记，具体如下：
1、在注册流程以及服务请求流程等特定流程中，主接入节点将业务流相关的业务数据包的转发通道先建立到本地，因此发送给接入和移动性管理功能的接入节点的IP地址和TEID是主接入节点分配的。因此，接入和移动性管理功能在上述特定流程中，收到接入节点的IP地址和TEID后，则将收到的IP地址对应的接入节点标记为第一基站。
例如：接入和移动性管理功能收到接入节点发送的初始上下文响应消息，获取消息中携带的接入节点的IP地址和TEID后，将该IP地址对应的接入节点标记为第一基站。
2、接入和移动性管理功能在确认用户设备的连接类型为双连接用户设备后，收到新的接入节点的IP地址则可以标记为第二基站；或者，如果接入和移动性管理功能收到多个接入节点的IP地址，则将同一个用户设备的，不同于标记为第一基站的用户面IP地址对应的接入节点标记为第二基站。
例如：在图4中的PDU会话资源更新指示消息是为双连接用户设备发送的，接入和移 动性管理功能收到该PDU会话资源更新指示消息后，可以从该PDU会话资源更新指示消息中获得接入节点的IP地址和TEID。如果，已经有被标记为第一基站的IP地址，而当前消息中携带的接入节点的IP地址不同于上述已经标记为第一基站的IP地址，则将该PDU会话资源更新指示消息中携带的IP地址对应的接入节点标记为第二基站。
进一步的，接入和移动性管理功能通过以上2个方法标记基站类型，该接入和移动性管理功能可用为此设置老化定时器，老化定时器超时后，将标记的基站类型清空，重新执行本实施例的学习过程。
基于上述的自学习过程，接入和移动性管理功能获知用户设备建立的业务流，哪些是建立在主接入节点上，哪些是建立在辅接入节点上。据此，接入和移动性管理功能可以参考前文移动管理设备识别用户设备的连接类型的方法，在此不再赘述。
进一步的，接入和移动性管理功能在通过自学习识别用户设备的接入点类型得到识别结果后，可以将该识别结果通知给会话管理设备、用户面功能以及策略控制功能。比如，将识别的接入点类型发送给会话管理设备、用户面功能以及策略控制功能；又比如，通过信令消息将用户为单连接用户设备或者双连接用户设备的信息通知给会话管理设备、用户面功能以及策略控制功能。
本申请还提供一种网络系统，如图8所示，包括：移动管理设备801和网关设备802；可以一并参考图1A、图1B、图1C以及图2所示的网络架构；
所述移动管理设备801，用于执行本发明实施例第一方面所提供的由移动管理设备所执行的方法流程，更具体例如，图3、图5以及图6中由移动管理设备所执行的方法流程、图4中由接入和移动管理功能所执行的方法流程；
所述网关设备802，用于依据从所述移动管理设备接收的连接类型对用户设备进行服务质量控制或者计费控制。
在本实施例中，由移动管理设备识别用户设备的连接类型并告知网关设备，网关设备可以据此对不同连接类型的用户设备执行不同的服务质量控制和计费控制。
在一个可能的实现方式中，所述网络系统还包括策略控制功能设备803、会话管理设备804或用户面功能设备805；
所述移动管理设备801，还用于向所述策略控制功能设备803、所述会话管理设备804或所述用户面功能设备805发送所述连接类型；
所述策略控制功能设备803，用于依据所述连接类型对所述用户设备下发服务质量策略或者计费控制策略；或者，
所述会话管理设备804，用于依据所述连接类型对所述用户设备进行服务质量控制或者计费控制；或者，
所述用户面功能设备805，用于依据所述连接类型对所述用户设备进行服务质量控制或者计费控制。
在本实施例中，由移动管理设备识别用户设备的连接类型后告知其他各种网络设备(策略控制功能设备803、会话管理设备804或用户面功能设备805等)，网络设备可以据此根据自己所负责的功能执行不同的控制，实现对不同连接类型的用户设备的差别服务。
本发明实施例还提供了一种移动管理设备，如图9所示，包括：
识别单元901，用于识别用户设备通过接入节点设备接入核心网所采用的连接类型，所述连接类型为单连接或双连接；在所述连接类型为单连接的情况下，所述用户设备通过1个接入节点设备接入所述核心网；在所述连接类型为双连接的情况下，所述用户设备通过两个接入节点设备接入所述核心网；以及
接入控制单元905，用于依据所述用户设备的连接类型，对所述用户设备进行接入控制。
本实施例中，由移动管理设备来识别用户设备的连接类型，可以将识别功能聚集在一个固定的设备中；另外，移动管理设备是用户设备经接接入节点设备首先接入的核心网设备，因此如果在移动管理设备进一步进行接入控制等针对性服务，相比于由其他设备识别后再通知移动管理设备更为及时，延迟更小。
本实施例的具体说明可以参考前文第一方面提供的方法实施例，以及图3、图5以及图6中由移动管理设备所执行的方法流程说明、图4中由接入和移动管理功能所执行的方法流程说明，在此不再赘述。
在一个可能的实现方式中，所述识别单元901，用于根据接入节点设备发送的所述用户设备的接入类型参数，确定所述用户设备的连接类型，所述接入类型参数用于指示所述用户设备的无线接入类型或所述接入节点设备的类型；
或者，根据所述用户设备的双连接能力、所述用户设备的签约信息以及所述移动管理设备的本地配置中的一项或多项，确定所述用户设备的连接类型；
或者，接收所述接入节点设备发送的数据使用报告，所述数据使用报告中包含用户设备的流量信息，根据所述数据使用报告确定所述用户设备的连接类型；
或者，接收携带所述接入节点设备的互联网协议IP地址的消息，根据所述接入节点设备的IP地址确定所述用户设备的连接类型。
在一个可能的实现方式中，所述识别单元901，用于根据所述接入节点设备发送的所述用户设备的接入类型参数，确定所述用户设备的连接类型包括：根据接入节点设备发送的无线接入承载更新请求消息，或通道切换请求消息，或业务流的通知消息中包含的接入类型参数，确定所述用户设备的连接类型。
在一个可能的实现方式中，所述识别单元901，用于接收携带所述接入节点设备的互联网协议IP地址的消息，根据所述接入节点设备的IP地址确定所述用户设备的连接类型包括：接收初始上下文建立响应消息，分组数据单元PDU会话资源建立响应消息或者缺省承载建立响应消息，在所述初始上下文建立响应消息，PDU会话资源建立响应消息或者缺省承载建立响应消息中携带所述接入节点设备的IP地址；根据所述接入节点设备的IP地址确定所述用户设备的连接类型。
在一个可能的实现方式中，所述识别单元901，用于根据所述用户设备的双连接能力、所述用户设备的签约信息以及所述移动管理设备的本地配置的一项或多项，确定所述用户设备的连接类型包括：
用于根据所述用户设备发送的所述用户设备的双连接能力的信息，确定所述用户设备的连接类型，或者，
用于根据从所述用户设备的归属用户服务器获取所述用户设备的签约信息，确定所述 用户设备的连接类型，或者，
用于根据所述移动管理设备的本地配置中包含的是否允许所述用户设备建立双连接的信息，确定所述用户设备的连接类型。
在一个可能的实现方式中，所述识别单元901，用于接收所述接入节点设备发送的数据使用报告，所述数据使用报告中包含用户设备的流量信息，所述移动管理设备根据所述数据使用报告确定所述用户设备的连接类型包括：用于确定在所述用户设备的连接态周期内，接收到接入节点设备发送的数据使用报告，则确定所述用户设备的连接类型为双连接。另一方面，若确定在所述用户设备的连接态周期内，没有接收到所述接入节点设备发送的数据使用报告，则确定所述用户设备的连接类型为单连接。
在一个可能的实现方式中，所述移动管理设备还包括：
标记单元903，用于根据接收的接入节点设备的IP地址，将接入节点设备区分为第一基站或第二基站；
所述识别单元901，具体用于在所述用户设备接入的接入节点设备包含第一基站和第二基站时，所述移动管理设备确定所述用户设备的连接类型为双连接；在所述用户设备接入的接入节点设备只包含第一基站时，所述移动管理设备确定所述用户设备的连接类型为单连接。
在一个可能的实现方式中，所述标记单元903，用于在所述用户设备不被允许建立双连接的情况下，所述移动管理设备在接收到所述接入节点设备的IP地址后，将所述接入节点设备的IP地址对应的接入节点设备标记为第一基站；获取业务数据包的转发通道建立到第一基站的流程中接收的接入节点设备的IP地址，将所述接入节点设备的IP地址对应的接入节点设备标记为第一基站；在所述用户设备接入两个IP地址，且其中一个IP地址对应的接入节点设备为第一基站时，将所述两个IP地址中的另一IP地址对应的接入节点设备标记为第二基站。
在一个可能的实现方式中，所述业务数据包的转发通道先建立到第一基站的流程包括：
注册流程、跟踪区域更新、服务请求流程以及附着流程中的任意一项。
在一个可能的实现方式中，所述移动管理设备还包括：
记录控制单元904，用于在所述标记单元903标记IP地址对应的接入节点设备为第一基站或第二基站后的预定时间之后，删除标记的IP地址对应的接入节点设备为第一基站或第二基站的信息。
在一个可能的实现方式中，所述移动管理设备还包括：
发送单元902，用于向网关设备发送识别的所述连接类型。
在本实施例中，识别单元901和除发送单元902外的其他单元可以对应到后续实施例中移动管理设备的处理器的相关功能，发送单元902可以对应到收发器的相关功能。
本发明实施例还提供了一种网络设备，该网络设备可以是移动管理设备、网关设备、策略控制功能设备、会话管理设备以及用户面功能设备中的任意一种。
如图10所示，该网络设备包括：处理器1001、存储器1002和收发器1003；所述述处理器1001、所述存储器1002和所述收发器1003以可通信方式连接；
在所述存储器1002中存储有程序代码；
如果该网络设备是移动管理设备，则所述处理器1001用于读取所述程序代码与所述收发器1003配合实现本发明实施例第一方面提供的实施例中，由网关设备除收发消息之外的方法流程，更具体例如：图3、图5以及图6中由移动管理设备所执行的方法流程、图4中由接入和移动管理功能所执行的方法流程，在此不再详述。
更具体地，其中，处理器1001可以对应到图9所示结构中的识别单元901、标记单元903、记录控制单元904,以及接入控制单元905的功能，具体执行过程本实施例不再详述。收发器1003可以对应到图9所示结构中发送单元902的功能，具体执行过程本实施例不再详述。
如果该网络设备是网关设备、策略控制功能设备、会话管理设备以及用户面功能设备，则收发器1003用于接收移动管理设备发送的用户设备的连接类型；处理器1001则用于依据用户设备的接入类型对用户设备进行相应的区别化服务。例如：所述策略控制功能设备依据所述连接类型对所述用户设备下发服务质量策略或计费控制策略。所述会话管理设备依据所述连接类型对所述用户设备进行服务质量控制或者计费控制。所述用户面功能设备依据所述连接类型对所述用户设备进行服务质量控制或者计费控制。所述网关设备依据所述连接类型对所述用户设备进行服务质量控制或者计费控制。
存储器1002包括但不限于是随机存储记忆体(random access memory，RAM)、只读存储器(read-only memory，ROM)、可擦除可编程只读存储器(erasable programmable read only memory，EPROM)、或便携式只读存储器(compact disc read-only memory，CD-ROM)，该存储器1002用于相关指令及数据。收发器1003用于接收和发送数据和消息。
处理器1001可以是一个或多个中央处理器(central processing unit，CPU)，在处理器1001是一个CPU的情况下，该CPU可以是单核CPU，也可以是多核CPU。
本发明实施例还提供了一种计算机存储介质，所述存储介质中存储有程序代码，所述程序代码包括程序指令，所述程序指令当被处理器执行时使所述处理器与收发器配合实现本发明实施例任意一项方法的功能，具体参阅前文中的方法流程，在此不再详述。
本发明实施例还提供了一种计算机程序产品，在上述计算机程序产品中包含程序指令，上述程序指令当被上述处理器执行时使处理器与收发器配合实现本发明实施例提供的任意一项方法的功能，具体参阅前文中的方法流程，在此不再详述。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程，该流程可以由计算机程序来指令相关的硬件完成，该程序可存储于计算机可读取存储介质中，该程序在执行时，可包括如上述各方法实施例的流程。而前述的存储介质包括：ROM或随机存储记忆体RAM、磁碟或者光盘等各种可存储程序代码的介质。

Claims (14)

  1. 一种对用户设备进行接入控制的方法，其特征在于，包括：
    移动管理设备识别用户设备通过接入节点设备接入核心网所采用的连接类型，所述连接类型为单连接或双连接；在所述连接类型为单连接的情况下，所述用户设备通过一个接入节点设备接入所述核心网；在所述连接类型为双连接的情况下，所述用户设备通过两个接入节点设备接入所述核心网；
    所述移动管理设备依据所述用户设备的连接类型，对所述用户设备进行接入控制。
  2. 根据权利要求1所述方法，其特征在于，所述移动管理设备识别用户设备通过接入节点设备接入核心网所采用的连接类型包括：
    所述移动管理设备接收接入节点设备发送的所述用户设备的接入类型参数，所述接入类型参数用于指示所述用户设备的无线接入类型或所述接入节点设备的类型；所述移动管理设备根据所述接入类型参数确定所述用户设备的连接类型；
    或者，所述移动管理设备根据所述用户设备的双连接能力、所述用户设备的签约信息以及所述移动管理设备的本地配置中的一项或多项，确定所述用户设备的连接类型；
    或者，所述移动管理设备接收接入节点设备发送的数据使用报告，所述数据使用报告中包含用户设备的流量信息，所述移动管理设备根据所述用户设备的流量信息确定所述用户设备的连接类型；
    或者，所述移动管理设备接收携带所述接入节点设备的互联网协议IP地址的消息，所述移动管理设备根据所述接入节点设备的IP地址确定所述用户设备的连接类型。
  3. 根据权利要求2所述方法，其特征在于，所述移动管理设备接收接入节点设备发送的所述用户设备的接入类型参数；所述移动管理设备根据所述接入类型参数确定所述用户设备的连接类型，包括：
    所述移动管理设备接收接入节点设备发送的无线接入承载更新请求消息，或通道切换请求消息，或业务流的通知消息；在所述无线接入承载更新请求消息，或所述通道切换请求消息，或所述业务流的通知消息中包含所述接入类型参数；所述移动管理设备根据所述接入类型参数确定所述用户设备的连接类型。
  4. 根据权利要求2所述方法，其特征在于，所述移动管理设备接收携带所述接入节点设备的互联网协议IP地址的消息，所述移动管理设备根据所述接入节点设备的IP地址确定所述用户设备的连接类型包括：
    所述移动管理设备接收初始上下文建立响应消息，分组数据单元PDU会话资源建立响应消息或者缺省承载建立响应消息，在所述初始上下文建立响应消息，PDU会话资源建立响应消息或者缺省承载建立响应消息中携带所述接入节点设备的IP地址；所述移动管理设备根据所述接入节点设备的IP地址确定所述用户设备的连接类型。
  5. 根据权利要求2所述方法，其特征在于，所述移动管理设备根据所述用户设备的双连接能力、所述用户设备的签约信息以及所述移动管理设备的本地配置的一项或多项，确定所述用户设备的连接类型包括：
    所述移动管理设备接收所述用户设备发送的所述用户设备的双连接能力的信息；所述移动管理设备根据所述用户设备的双连接能力的信息，确定所述用户设备的连接类型，或者，
    所述移动管理设备从所述用户设备的归属用户服务器获取所述用户设备的签约信息，根据所述签约信息确定所述用户设备的连接类型，或者，
    所述移动管理设备获取所述移动管理设备的本地配置，在所述本地配置中包含是否允许所述用户设备建立双连接的信息；所述移动管理设备依据所述本地配置确定所述用户设备的连接类型。
  6. 根据权利要求2所述方法，其特征在于，所述移动管理设备根据接收所述接入节点设备发送的数据使用报告，所述数据使用报告中包含用户设备的流量信息，所述移动管理设备根据所述数据使用报告确定所述用户设备的连接类型包括：
    所述移动管理设备确定在所述用户设备的连接态周期内，接收到所述接入节点设备发送的所述数据使用报告，则确定所述用户设备的连接类型为双连接。
  7. 根据权利要求2所述方法，其特征在于，所述移动管理设备根据接收的接入节点设备的IP地址，确定所述用户设备的连接类型包括：
    所述移动管理设备根据接收的接入节点设备的IP地址，将接入节点设备区分为第一基站或第二基站；
    在所述用户设备接入的接入节点设备包含第一基站和第二基站时，所述移动管理设备确定所述用户设备的连接类型为双连接。
  8. 根据权要求1至7任意一项所述方法，其特征在于，所述方法还包括：
    所述移动管理设备向网关设备发送识别的所述连接类型。
  9. 一种接入类型的识别方法，其特征在于，包括：
    接入节点设备确定用户设备的接入类型参数，向移动管理设备发送用户设备的接入类型参数，所述接入类型参数用于指示所述用户设备的无线接入类型或接入节点设备的类型；
    所述移动管理设备接收所述接入节点设备发送的所述用户设备的接入类型参数，根据所述接入类型参数确定所述用户设备的连接类型。
  10. 根据权利要求9所述方法，其特征在于，所述向移动管理设备发送用户设备的接入类型参数包括：
    所述接入节点设备向所述移动管理设备发送无线接入承载更新请求消息，或通道切换请求消息，或业务流的通知消息；在所述无线接入承载更新请求消息，或所述通道切换请求消息，或所述业务流的通知消息中包含所述接入类型参数。
  11. 一种网络系统，其特征在于，包括：
    移动管理设备和网关设备；
    所述移动管理设备，用于执行权利要求8所述的方法流程；
    所述网关设备，用于依据从所述移动管理设备接收的连接类型对用户设备进行服务质量控制或者计费控制。
  12. 权利要求11所述网络系统，其特征在于，所述网络系统还包括：
    策略控制功能设备、会话管理设备或用户面功能设备；
    所述移动管理设备，还用于向所述策略控制功能设备、所述会话管理设备或所述用户面功能设备发送所述连接类型；
    所述策略控制功能设备，用于依据所述连接类型对所述用户设备下发服务质量策略或计费控制策略；或者，
    所述会话管理设备，用于依据所述连接类型对所述用户设备进行服务质量控制或者计费控制；或者，
    所述用户面功能设备，用于依据所述连接类型对所述用户设备进行服务质量控制或者计费控制。
  13. 一种移动管理设备，包括：处理器、存储器和收发器；所述述处理器、所述存储器和所述收发器以可通信方式连接；其特征在于，
    在所述存储器中存储有程序代码；
    所述处理器用于读取所述程序代码与所述收发器配合实现权利要求1至11任意一项的方法的功能。
  14. 一种计算机存储介质，其特征在于，
    所述存储介质中存储有程序代码，所述程序代码包括程序指令，所述程序指令当被处理器执行时使所述处理器与收发器配合实现权利要求1至8任意一项方法的功能。
PCT/CN2020/097542 2019-08-02 2020-06-22 对用户设备进行接入控制的方法，网络系统及相关设备 WO2021022919A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP20850785.5A EP3972376A4 (en) 2019-08-02 2020-06-22 METHOD OF PERFORMING ACCESS CONTROL ON A USER EQUIPMENT, NETWORK SYSTEM AND ASSOCIATED DEVICE
US17/586,140 US20220150797A1 (en) 2019-08-02 2022-01-27 Method for performing access control on user equipment, network system, and related device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910713959.2 2019-08-02
CN201910713959.2A CN112312585B (zh) 2019-08-02 2019-08-02 对用户设备进行接入控制的方法，网络系统及相关设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/586,140 Continuation US20220150797A1 (en) 2019-08-02 2022-01-27 Method for performing access control on user equipment, network system, and related device

Publications (1)

Publication Number Publication Date
WO2021022919A1 true WO2021022919A1 (zh) 2021-02-11

Family

ID=74485277

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/097542 WO2021022919A1 (zh) 2019-08-02 2020-06-22 对用户设备进行接入控制的方法，网络系统及相关设备

Country Status (4)

Country Link
US (1) US20220150797A1 (zh)
EP (1) EP3972376A4 (zh)
CN (1) CN112312585B (zh)
WO (1) WO2021022919A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11765052B1 (en) 2022-03-11 2023-09-19 T-Mobile Usa, Inc. User equipment hosting for customizable 5G services

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115618369A (zh) * 2021-07-14 2023-01-17 深圳富联富桂精密工业有限公司 远程访问方法、电子设备及存储介质
WO2023168625A1 (en) * 2022-03-09 2023-09-14 Nokia Shanghai Bell Co., Ltd. Improving data transmission in telecommunication systems

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015133144A1 (en) * 2014-03-06 2015-09-11 Nec Corporation Apparatus, system and method for small cell enhancement / dual connectivity
CN105557035A (zh) * 2013-08-09 2016-05-04 阿尔卡特朗讯 处于双重连接的用户设备之间的数据流的设置或修改

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015136122A1 (en) * 2014-03-14 2015-09-17 Nec Europe Ltd. Method, user equipment, master evolved node b and communication system for dual connectivity
EP3449654A1 (en) * 2016-04-27 2019-03-06 INTEL Corporation Systems, methods and devices for indicating support of more than one data radio bearer for cellular internet of things devices
WO2018172408A1 (en) * 2017-03-21 2018-09-27 Nokia Solutions And Networks Oy Radio-access-technology-specific access restrictions
KR102047708B1 (ko) * 2017-06-15 2019-11-22 엘지전자 주식회사 요청에 대한 응답 방법 및 네트워크 장치

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105557035A (zh) * 2013-08-09 2016-05-04 阿尔卡特朗讯 处于双重连接的用户设备之间的数据流的设置或修改
WO2015133144A1 (en) * 2014-03-06 2015-09-11 Nec Corporation Apparatus, system and method for small cell enhancement / dual connectivity

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
NTT DOCOMO; NOKIA; ALCATEL-LUCENT SHANGHAI BELL; BROADCOM: "Procedures for Dual Connectivity", 3GPP DRAFT; S2-174985_WAS_4573 23502 DUAL CONNECTIVITY V1, vol. SA WG2, 3 July 2017 (2017-07-03), San Jose del Cabo, Mexico, pages 1 - 10, XP051310005 *
SAMSUNG: "Support of CSG, LIPA, and SIPTO@LN functions for dual connectivity", 3GPP DRAFT; S2-160107, vol. SA WG2, 19 January 2016 (2016-01-19), pages 1 - 4, XP051072019 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11765052B1 (en) 2022-03-11 2023-09-19 T-Mobile Usa, Inc. User equipment hosting for customizable 5G services

Also Published As

Publication number Publication date
EP3972376A1 (en) 2022-03-23
EP3972376A4 (en) 2022-07-13
US20220150797A1 (en) 2022-05-12
CN112312585B (zh) 2023-10-20
CN112312585A (zh) 2021-02-02

Similar Documents

Publication Publication Date Title
JP6972023B2 (ja) 無線通信システムの端末の方法、無線通信システムの基地局の方法、端末、及び基地局
US11160002B2 (en) Method for supporting handover and corresponding apparatus
US11129054B2 (en) Methods, systems and devices for supporting local breakout in small cell architecture
US9320075B2 (en) Method, system and transmission distribution network element for indicating data-distribution
JP5406220B2 (ja) ユーザ装備の位置情報を更新するための方法
US8971290B2 (en) Handover method supporting terminal mobility
US9380551B2 (en) Method and terminal for performing detach procedure
JP5637138B2 (ja) 通信システムと通信制御方法
US11729693B2 (en) Method for supporting handover and corresponding apparatus
WO2021022919A1 (zh) 对用户设备进行接入控制的方法，网络系统及相关设备
US20110317560A1 (en) MOBILE COMMUNICATION SYSTEM, QoS CONTROL STATION AND MOBILE STATION
US20200008265A1 (en) Method for avoiding handover failure
CA2757357A1 (en) Server for control plane at mobile communication network and method for controlling establishment of connection thereof
JP2020522954A (ja) Ｐｄｕセッションのハンドオーバを決定する方法及びセル
JP2013529039A (ja) ハンドオーバ方法、通信デバイス及び通信システム
EP3445081B1 (en) Flow-based bearer management method and device
WO2019223639A1 (zh) 无线通信方法和设备
US11950143B2 (en) Method and device for supporting handover
WO2011143997A1 (zh) 一种实现路由选择的方法和装置
JP2022521088A (ja) ポリシー管理方法及び装置
WO2020228770A1 (zh) 一种承载修改方法及接入网设备
CN111629406B (zh) 一种切换处理的方法、相关设备、程序产品以及存储介质
US11523309B2 (en) Method and device for supporting handover
US8774132B2 (en) Base station device, base station controlling device, mobile terminal, communication system, and method for controlling base station device
WO2014071798A1 (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: 20850785

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2020850785

Country of ref document: EP

Effective date: 20211217

NENP Non-entry into the national phase

Ref country code: DE