WO2018023220A1 - 一种业务数据传输方法及设备 - Google Patents

一种业务数据传输方法及设备 Download PDF

Info

Publication number
WO2018023220A1
WO2018023220A1 PCT/CN2016/092521 CN2016092521W WO2018023220A1 WO 2018023220 A1 WO2018023220 A1 WO 2018023220A1 CN 2016092521 W CN2016092521 W CN 2016092521W WO 2018023220 A1 WO2018023220 A1 WO 2018023220A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
service data
service
terminal
sent
Prior art date
Application number
PCT/CN2016/092521
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 CN201680087317.0A priority Critical patent/CN109417729B/zh
Priority to PCT/CN2016/092521 priority patent/WO2018023220A1/zh
Priority to EP16910818.0A priority patent/EP3484203B1/en
Publication of WO2018023220A1 publication Critical patent/WO2018023220A1/zh
Priority to US16/261,026 priority patent/US10932133B2/en
Priority to US17/161,274 priority patent/US20210153020A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/08—Access security
    • 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
    • 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/64—On-line charging system [OCS]
    • 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/65—Off-line 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/66—Policy and charging system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/18—Negotiating wireless communication parameters
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/20—Services signaling; Auxiliary data signalling, i.e. transmitting data via a non-traffic channel
    • 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
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/30—Services specially adapted for particular environments, situations or purposes
    • H04W4/38—Services specially adapted for particular environments, situations or purposes for collecting sensor information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/80—Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/56—Allocation or scheduling criteria for wireless resources based on priority criteria
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08—Mobility data transfer
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/08—Upper layer protocols
    • H04W80/10—Upper layer protocols adapted for application session management, e.g. SIP [Session Initiation Protocol]
    • 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/16—Gateway arrangements
    • 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
    • H04W88/184—Messaging devices, e.g. message centre
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a service data transmission method and device.
  • IoT Internet of Things
  • the 3rd Generation Partnership Project (English: the 3rd Generation Partnership Project, 3GPP) is conducting research on the Narrow Band Internet of Things (NB-IoT) project, which is supported by the enhancement of the overall architecture. Ultra-low complexity, power limited, low data rate IoT devices.
  • NB-IoT terminals such as water meters, electricity meters, sensors, etc., mainly send meter reading data or monitoring data with a small amount of data, for example, generally only tens to hundreds of bytes, and the transmission interval is large. Therefore, in order to avoid waste of transmission resources, the small data packet of the NB-IoT terminal is encapsulated and transmitted in a non-access stratum (English: Non-Access Stratum, NAS for short) signaling message.
  • a non-access stratum English: Non-Access Stratum, NAS for short
  • the network side cannot know the service data information of the NB-IoT terminal, and the network side cannot provide targeted services for different types of NB-IoT services.
  • the present invention provides a service data transmission method and device, which are used to solve the problem that the network side in the prior art cannot provide targeted services for different types of NB-IoT services.
  • an embodiment of the present invention provides a service data transmission method, including:
  • the access network device determines first information of the service data to be sent by the terminal, where the first information includes at least one of a service type and a priority; and then the access network device receives the terminal and passes the terminal The service data sent by the NAS signaling message; the access network device sends the service data and the first information to a gateway by using a mobility management entity, where the gateway receives the service data and the After the information, the service data is charged according to the first information.
  • the access network determines the first information of the service data to be sent by the terminal, and then the access network device sends the determined first information to the gateway, so that the service data of the gateway to the terminal.
  • the billing service is provided, thereby solving the problem that the prior art cannot provide targeted services for different types of NB-IoT services caused by the network side transmitting service data through the NAS signaling message.
  • the access network device After the access network device determines the first information of the service data to be sent by the terminal, the access network device receives the location that the terminal sends through the non-access stratum NAS signaling message. Before the service data is described, the access network device performs transmission resource management on the service data according to the first information. Specifically, the access network device allocates a transmission resource for the terminal to transmit the service data according to the first information, so that the terminal sends the service data to the access network by using the transmission resource allocated by the access network device. device.
  • the access network device determines the first information of the service data to be sent by the terminal, which can be implemented as follows:
  • the access network device receives the first information sent by the terminal.
  • the access network device receives the second information sent by the terminal, where the second information includes a service type and/or a priority used by the terminal to request to transmit the service data;
  • the second information is sent to the mobility management entity;
  • the access network device receives the first service authorization information sent by the mobility management entity, where the first service authorization information is used to indicate that the terminal is allowed to transmit the service data.
  • the service type and/or priority adopted; the access network device determines the first information according to the first service authorization information.
  • the first service authorization information may include indication information, where the indication information is used to indicate that the second information is allowed.
  • an embodiment of the present invention provides a service data transmission method, including:
  • the mobility management entity receives the non-access stratum NAS signaling message, where the NAS signaling message carries the service data of the terminal; the mobility management entity acquires the first information of the service data, where the first information includes the service data At least one of a service type and a priority of the service data; the mobility management entity transmitting the service data and the first information to a gateway, the gateway receiving the service data and the first After the information, the service data is charged based on the first information.
  • the mobility management entity obtains the first information of the service data, and sends the first information to the gateway, so that the gateway provides the charging service to the service data of the terminal, thereby solving the problem.
  • the prior art cannot provide targeted services for different types of NB-IoT services on the network side caused by transmitting service data through NAS signaling messages.
  • the first information that the mobility management entity acquires the service data may be implemented as follows:
  • the mobility management entity receives the first information sent by the access network device.
  • the mobility management entity receives the first information that is sent by the terminal by using a non-access stratum NAS signaling message.
  • the mobility management entity before the mobile management entity receives the first information sent by the access network device, the mobility management entity receives second information sent by the access network device,
  • the second information includes a service type and/or a priority that the terminal requests to transmit the service data, and the mobility management entity authorizes the second information according to the subscription information of the terminal to obtain a first service authorization.
  • the first service authorization information is used to indicate a service type and/or a priority used by the terminal to transmit the service data, and the mobility management entity sends the first service authorization information to the And the network access device, so that the access network device determines the first information based on the first service authorization information.
  • the first information that the mobility management entity acquires the service data may be implemented as follows:
  • the mobility management entity receives the first information sent by the terminal.
  • an embodiment of the present invention provides a service data transmission method, including:
  • the gateway receives the service data of the terminal sent by the mobility management entity and the first information of the service data, where the first information includes at least one of a service type and a priority;
  • the gateway performs charging on the service data according to the first information.
  • an embodiment of the present invention provides a service data transmission method, including:
  • the access network device receives the service data sent by the mobility management entity through the non-access stratum NAS signaling message; the access network device receives the information of the service data sent by the mobility management entity, where the information of the service data includes At least one of a service type of the service data and a priority of the service data; the access network device performs transmission resource management on the service data according to the information of the service data.
  • the mobility management entity sends the service data and the service data information to the access network device, and the access network device allocates the transmission resource to the terminal to transmit the service data based on the service data, thereby solving the prior art.
  • the network side that is caused by transmitting service data through NAS signaling messages cannot provide targeted services for different types of NB-IoT services.
  • the embodiment of the present invention further provides a service data transmission method, including:
  • the mobility management entity receives the service data of the terminal sent by the gateway; the mobility management entity acquires the first information of the service data, where the first information includes at least one of a service type and a priority; the mobility management entity
  • the access network device sends a non-access stratum NAS signaling message, where the NAS signaling message carries the service data; the mobility management entity sends the first information to the access network device, where the access After receiving the first information, the network device performs transmission resource management on the service data according to the first information.
  • the mobility management entity After receiving the service data of the terminal, the mobility management entity obtains the first information of the service data, and then sends the service data and the first information of the service data to the access network device, so that the access network device is configured according to the first information.
  • the service data is used for transmission resource management, thereby solving the problem that the network side cannot provide targeted services for different types of NB-IoT services caused by the transmission of service data through NAS signaling messages.
  • the mobility management entity acquires the first part of the service data.
  • Information can be achieved as follows:
  • the mobility management entity determines the first information according to the subscription information of the terminal.
  • the first information is carried in a packet header of the data packet of the service data, and the mobility management entity acquires the first information from a packet header of the data packet of the service data.
  • an embodiment of the present invention provides a service data transmission method, including:
  • the mobility management entity receives a request message, where the request message includes transmission mode indication information, where the transmission mode indication information is used to indicate that the terminal uses the non-access stratum NAS signaling message to transmit service data; if the mobility management entity is in accordance with the request Determining, by the message, that the terminal transmits the service data by using a non-access stratum NAS signaling message, the mobility management entity determining, according to the subscription information of the terminal, the second service authorization information of the terminal, the second service The authorization information includes information indicating a type of service and/or a priority used to allow the terminal to transmit service data; the mobility management entity transmits the second service authorization information to the terminal.
  • the mobile management entity sends the second service authorization information of the terminal to the terminal when determining that the terminal uses the NAS signaling message to transmit the service data, so that the terminal determines the sent service data based on the second service authorization information.
  • the network side cannot provide targeted service issues for different types of NB-IoT services.
  • the second service authorization information further includes first quota information, where the first quota information is used to indicate that the number of service data of the service type is allowed to be sent within a specific time.
  • the service authorization information further includes second quota information, where the second quota information is used to indicate the quantity of the priority service data that is allowed to be sent in a specific time.
  • an embodiment of the present invention provides a service data transmission method, including:
  • the terminal sends a request message to the mobility management entity, where the request message includes transmission mode indication information, where the transmission mode indication information is used to indicate that the terminal uses the non-access stratum NAS signaling message to transmit service data; the terminal receives the mobility management a second service authorization information sent by the entity, where the second service authorization information includes information indicating a service type and/or a priority used by the terminal to transmit the service data; the terminal is authorized according to the second service And determining information of the service data, where the information of the service data includes at least one of a service type of the service data and a priority of the service data; the terminal sends the information of the service data to The access network device.
  • the mobile management entity sends the second service authorization information of the terminal to the terminal when determining that the terminal uses the NAS signaling message to transmit the service data, so that the terminal determines the sent service data based on the second service authorization information.
  • the network side cannot provide targeted service issues for different types of NB-IoT services.
  • the second service authorization information further includes first quota information, where the first quota information is used to indicate the number of service data that is allowed to be sent in the specific time.
  • the second service authorization information further includes second quota information, where the quota information is used to indicate the number of service data that is allowed to send the priority in a specific time.
  • the eighth aspect of the present invention provides an access network device, including:
  • a processor configured to determine first information of service data to be sent by the terminal, where the first information includes at least one of a service type and a priority;
  • a receiver configured to receive the service data that is sent by the terminal by using a non-access stratum NAS signaling message
  • a communication interface configured to send the service data received by the receiver and the first information determined by the processor to a gateway by using a mobility management entity, so that the gateway is configured according to the first information
  • the business data is billed.
  • the receiver receives the service data sent by the terminal through the non-access stratum NAS signaling message.
  • the processor is further configured to perform transmission resource management on the service data according to the first information.
  • the receiver is further configured to receive the first information sent by the terminal.
  • the receiver is further configured to receive second information sent by the terminal, where the second information includes a service type and/or priority used by the terminal to request to transmit the service data. level;
  • the communication interface is further configured to send the second information to a mobility management entity
  • the communication interface is further configured to receive first service authorization information sent by the mobility management entity, where the first service authorization information is used to indicate a service type and/or priority that is allowed to be used by the terminal to transmit the service data. level;
  • the processor is specifically configured to determine the first information according to the first service authorization information.
  • the first service authorization information includes indication information, and the indication information is used to indicate that the second information is allowed.
  • a ninth aspect, the embodiment of the present invention provides a mobility management entity, including:
  • a communication interface configured to receive a non-access stratum NAS signaling message, where the NAS signaling message carries service data of the terminal;
  • a processor configured to acquire first information of the service data received by the communication interface, where the first information includes at least one of a service type of the service data and a priority of the service data;
  • the communication interface is further configured to send the service data and the first information to a gateway, so that the gateway performs charging on the service data.
  • the communication interface is further configured to receive the first information sent by the access network device;
  • the communication interface is further configured to receive, by the terminal, a non-access stratum NAS signaling message.
  • the first information is further configured to receive, by the terminal, a non-access stratum NAS signaling message.
  • the communication interface is further configured to receive second information sent by the access network device before receiving the first information sent by the access network device, where the second The information includes a service type and/or a priority used by the terminal to request to transmit the service data;
  • the processor is further configured to: according to the subscription information of the terminal, authorize the second information to obtain first service authorization information, where the first service authorization information is used to indicate that the terminal is allowed to transmit the service data.
  • the communication interface is further configured to send the first service authorization information to the access network device, so that the access network device determines the first information based on the first service authorization information.
  • the receiver is further configured to receive the first information sent by the terminal.
  • the tenth aspect of the present invention provides a gateway, including:
  • a communication interface configured to receive service data of the terminal sent by the mobility management entity and first information of the service data, where the first information includes at least one of a service type and a priority;
  • a processor configured to perform charging on the service data according to the first information received by the communication interface.
  • an access network device including:
  • a communication interface configured to receive service data sent by the mobility management entity by using a non-access stratum NAS signaling message; and receive information about the service data sent by the mobility management entity, where the information of the service data includes a service type and a priority At least one of the stages;
  • a processor configured to perform transmission resource management on the service data according to the information of the service data.
  • the embodiment of the present invention provides a mobility management entity, including:
  • a communication interface configured to receive service data of the terminal sent by the gateway
  • a processor configured to acquire first information of the service data received by the communication interface, where the first information includes at least one of a service type and a priority;
  • the communication interface is configured to send a non-access stratum NAS signaling message to the access network device, where The NAS signaling message carries the service data; and the first information is sent to the access network device, so that the access network device performs transmission resource management on the service data according to the first information.
  • the processor is specifically configured to determine the first information according to the subscription information of the terminal;
  • the first information is carried in a packet header of the data packet of the service data, where the processor is specifically configured to obtain the first information from a packet header of the data packet of the service data.
  • the embodiment of the present invention provides a mobility management entity, including:
  • a communication interface configured to receive a request message, where the request message includes a transmission mode indication information, where the transmission mode indication information is used to indicate that the terminal transmits the service data by using a non-access stratum NAS signaling message;
  • a processor configured to determine, according to the request message, that the terminal transmits the service data by using a non-access stratum NAS signaling message, determining, according to the subscription information of the terminal, the second service authorization information of the terminal.
  • the second service authorization information includes information indicating a service type and/or a priority used by the terminal to allow the service data to be transmitted;
  • the communication interface is further configured to send the second service authorization information to the terminal.
  • the second service authorization information further includes first quota information, where the first quota information is used to indicate that the number of service data of the service type is allowed to be sent within a specific time.
  • the service authorization information further includes second quota information, where the second quota information is used to indicate the quantity of the priority service data that is allowed to be sent in a specific time.
  • the embodiment of the present invention provides a terminal, including:
  • a transmitter configured to send a request message to the mobility management entity, where the request message includes transmission mode indication information, where the transmission mode indication information is used to indicate that the terminal transmits the service data by using a non-access stratum NAS signaling message;
  • a receiver configured to receive second service authorization information sent by the mobility management entity, where
  • the second service authorization information includes information indicating a service type and/or a priority used by the terminal to transmit the service data;
  • a processor configured to determine information of the service data according to the second service authorization information, where the information of the service data includes at least one of a service type of the service data and a priority of the service data;
  • the transmitter is further configured to send information about the service data determined by the processor to the access network device.
  • the second service authorization information further includes first quota information, where the first quota information is used to indicate the number of service data that is allowed to be sent in the specific time.
  • the second service authorization information further includes second quota information, where the quota information is used to indicate the number of service data that is allowed to send the priority in a specific time.
  • an embodiment of the present invention provides an access network device, including:
  • a determining unit configured to determine first information of the service data to be sent by the terminal, where the first information includes at least one of a service type and a priority;
  • a receiving unit configured to receive the service data that is sent by the terminal by using a non-access stratum NAS signaling message
  • a sending unit configured to send the service data received by the receiving unit and the first information determined by the determining unit to a gateway by using a mobility management entity, so that the gateway is configured according to the first information
  • the business data is billed.
  • the method further includes: a management unit, configured to: after the determining unit determines the first information of the service data to be sent by the terminal, the receiving unit receives the non-access stratum NAS signaling by the terminal Before the service data sent by the message, the transmission resource management is performed on the service data according to the first information.
  • a management unit configured to: after the determining unit determines the first information of the service data to be sent by the terminal, the receiving unit receives the non-access stratum NAS signaling by the terminal Before the service data sent by the message, the transmission resource management is performed on the service data according to the first information.
  • the determining unit is specifically configured to determine the first information when the receiving unit receives the first information sent by the terminal.
  • the receiving unit is further configured to receive a second sent by the terminal.
  • Information includes a service type and/or a priority used by the terminal to request to transmit the service data;
  • the sending unit is further configured to send the second information to the mobility management entity
  • the receiving unit is further configured to receive first service authorization information sent by the mobility management entity, where the first service authorization information is used to indicate a service type and/or priority that is allowed to be used by the terminal to transmit the service data. level;
  • the determining unit is specifically configured to determine the first information according to the first service authorization information.
  • the first service authorization information includes indication information, and the indication information is used to indicate that the second information is allowed.
  • the embodiment of the present invention provides a mobility management entity, including:
  • a receiving unit configured to receive a non-access stratum NAS signaling message, where the NAS signaling message carries service data of the terminal;
  • An acquiring unit configured to acquire first information of the service data received by the receiving unit, where the first information includes at least one of a service type of the service data and a priority of the service data;
  • a sending unit configured to send the service data and the first information to a gateway, so that the gateway performs charging on the service data.
  • the acquiring unit is specifically configured to: when the receiving unit receives the first information sent by the access network device, obtain the first information; or
  • the acquiring unit is specifically configured to acquire the first information when the receiving unit receives the first information that is sent by the terminal by using a NAS signaling message.
  • the receiving unit before receiving the first information sent by the access network device, is further configured to receive second information sent by the access network device, where the second information is And including a service type and/or a priority used by the terminal to request to transmit the service data;
  • the mobility management entity further includes an authorization unit, configured to authorize the second information according to the subscription information of the terminal to obtain first service authorization information, where the first service authorization information is used. Indicates a service type and/or priority that the terminal is allowed to transmit the service data;
  • the sending unit is further configured to send the first service authorization information to the access network device, so that the access network device determines the first information based on the first service authorization information.
  • the acquiring unit is specifically configured to acquire the first information when the receiving unit receives the first information sent by the terminal.
  • the embodiment of the present invention provides a gateway, including:
  • a receiving unit configured to receive service data of the terminal sent by the mobility management entity and first information of the service data, where the first information includes at least one of a service type and a priority;
  • the charging unit is configured to perform charging on the service data according to the first information.
  • the embodiment of the present invention further provides an access network device, including:
  • a receiving unit configured to receive service data that is sent by the mobility management entity by using a non-access stratum NAS signaling message; and receive information about the service data sent by the mobility management entity, where the information of the service data includes the service data At least one of a service type and a priority of the service data;
  • a management unit configured to perform transmission resource management on the service data according to the information of the service data received by the receiving unit.
  • the embodiment of the present invention provides a mobility management entity, including:
  • a receiving unit configured to receive service data of a terminal sent by the gateway
  • An acquiring unit configured to acquire first information of the service data received by the receiving unit, where the first information includes at least one of a service type of the service data and a priority of the service data;
  • a sending unit configured to send a non-access stratum NAS signaling message to the access network device, where the NAS signaling message carries the service data acquired by the acquiring unit, and sends the first information to the
  • the network access device is configured to enable the access network device to perform transmission resource management on the service data according to the first information.
  • the acquiring unit is specifically configured to determine the first information according to the subscription information of the terminal.
  • the first information is carried in a packet header of the data packet of the service data, and the acquiring unit is configured to obtain the first information from a packet header of the data packet of the service data.
  • the embodiment of the present invention provides a mobility management entity, including:
  • a receiving unit configured to receive a request message, where the request message includes transmission mode indication information, where the transmission mode indication information is used to indicate that the terminal transmits the service data by using a non-access stratum NAS signaling message;
  • a determining unit configured to determine, according to the request message, that the terminal transmits the service data by using a non-access stratum NAS signaling message, and determining, according to the subscription information of the terminal, the second service authorization information of the terminal,
  • the second service authorization information includes information indicating a service type and/or a priority used by the terminal to transmit service data;
  • a sending unit configured to send the second service authorization information determined by the determining unit to the terminal.
  • the second service authorization information further includes first quota information, where the first quota information is used to indicate that the number of service data of the service type is allowed to be sent within a specific time.
  • the service authorization information further includes second quota information, where the second quota information is used to indicate the quantity of the priority service data that is allowed to be sent in a specific time.
  • an embodiment of the present invention provides a terminal, including:
  • a sending unit configured to send a request message to the mobility management entity, where the request message includes transmission mode indication information, where the transmission mode indication information is used to indicate that the terminal uses the non-access stratum NAS signaling message to transmit service data;
  • a receiving unit configured to receive second service authorization information sent by the mobility management entity, where the second service authorization information includes information used to indicate a service type and/or a priority used by the terminal to transmit service data;
  • a determining unit configured to determine information of the service data according to the second service authorization information received by the receiving unit, where the information of the service data includes a service type of the service data And at least one of a priority of the business data;
  • the sending unit is further configured to send information about the service data determined by the determining unit to the access network device.
  • the second service authorization information further includes first quota information, where the first quota information is used to indicate the number of service data that is allowed to be sent in the specific time.
  • the second service authorization information further includes second quota information, where the quota information is used to indicate the number of service data that is allowed to send the priority in a specific time.
  • FIG. 1 is a structural diagram of an EPS network system according to an embodiment of the present invention
  • FIG. 2 is a flowchart of a service data transmission method according to Embodiment 1 of the present invention.
  • FIG. 3 is a flowchart of another service data transmission method according to Embodiment 1 of the present invention.
  • FIG. 5 is a flowchart of still another method for transmitting service data according to Embodiment 1 of the present invention.
  • FIG. 6 is a schematic diagram of a service data transmission method according to Embodiment 1 of the present invention.
  • FIG. 7 is a schematic diagram of another service data transmission method according to Embodiment 1 of the present invention.
  • FIG. 8 is a flowchart of still another method for transmitting service data according to Embodiment 1 of the present invention.
  • FIG. 9 is a schematic diagram of still another method for transmitting service data according to Embodiment 1 of the present invention.
  • FIG. 10 is a flowchart of a service data transmission method according to Embodiment 2 of the present invention.
  • FIG. 11 is a schematic diagram of a service data transmission method according to Embodiment 2 of the present invention.
  • FIG. 12 is a flowchart of a service data transmission method according to Embodiment 3 of the present invention.
  • FIG. 13 is a schematic diagram of a service data transmission method according to Embodiment 3 of the present invention.
  • FIG. 14 is a schematic diagram of an access network device according to an embodiment of the present disclosure.
  • FIG. 15 is a schematic diagram of another access network device according to an embodiment of the present disclosure.
  • FIG. 16 is a schematic diagram of a mobility management entity according to an embodiment of the present invention.
  • FIG. 17 is a schematic diagram of another mobility management entity according to an embodiment of the present invention.
  • FIG. 18 is a schematic diagram of a gateway according to an embodiment of the present disclosure.
  • FIG. 19 is a schematic diagram of another gateway according to an embodiment of the present disclosure.
  • FIG. 20 is a schematic diagram of still another access network device according to an embodiment of the present disclosure.
  • FIG. 21 is a schematic diagram of still another access network device according to an embodiment of the present disclosure.
  • FIG. 22 is a schematic diagram of still another mobility management entity according to an embodiment of the present invention.
  • FIG. 23 is a schematic diagram of still another mobility management entity according to an embodiment of the present invention.
  • FIG. 24 is a schematic diagram of still another mobility management entity according to an embodiment of the present invention.
  • FIG. 25 is a schematic diagram of still another mobility management entity according to an embodiment of the present invention.
  • FIG. 26 is a schematic diagram of a terminal according to an embodiment of the present disclosure.
  • FIG. 27 is a schematic diagram of another terminal according to an embodiment of the present invention.
  • the present invention provides a service data transmission method and device, which are used to solve the problem that the network side in the prior art cannot provide targeted services for different types of NB-IoT services.
  • the method and the device are based on the same inventive concept. Since the principles of the method and the device for solving the problem are similar, the implementation of the device and the method can be referred to each other, and the repeated description is not repeated.
  • the "and/or" used in the embodiments of the present invention may be a relationship of "and” or an "or” relationship, such as A and/or B, which may be either A alone or B alone. It can be A and B.
  • a terminal may be referred to as a user equipment (English: User Equipment, abbreviated as: UE), a mobile station (English: Mobile Station, abbreviated as: MS), or a mobile terminal (Mobile Terminal).
  • the terminal can communicate with one or more core network devices via a radio access network (English: Radio Access Network, RAN for short), for example,
  • the terminal may be a mobile phone (or "cellular" phone) or a computer with a mobile terminal, etc., for example, the terminal may also be a portable, pocket, handheld, computer built-in or in-vehicle mobile device with wireless access.
  • the network exchanges voice and/or data.
  • the embodiment of the present invention is described by taking an application to an EPS system as an example.
  • Figure 1 shows the architecture of the EPS network system.
  • the EPS network system includes: a UE, an evolved universal terrestrial radio access network (English: Evolved universal terrestrial radio access network, referred to as EUTRAN), a mobility management entity (English: Mobility Management Entity, MME for short), and a service gateway ( English: Serving Gateway, referred to as: S-GW), Packet Data Network Gateway (English: Packet Data Network Gateway, P-GW for short), Serving GPRS Support Node (English: Serving GPRS Support Node, SGSN for short), attribution signing User Server (English: Home Subscriber Server, HSS for short), Policy and Charging Rules Function (English: Policy and Charging Rules Function, PCRF) and Carrier Internet Protocol (English: Internet Protocol, IP for short) (Operator's IP Services).
  • EUTRAN Evolved universal terrestrial radio access network
  • MME Mobility Management Entity
  • S-GW Serving Gateway
  • EUTRAN A network consisting of multiple Evolved Node Bs (abbreviations: eNBs) that implements wireless physical layer functions, resource scheduling and radio resource management, radio access control, and mobility management functions.
  • the eNB is connected to the serving gateway (English: Serving Gateway, S-GW for short) through the user plane interface S1-U for transmitting user data; and is connected to the MME through the control plane interface S1-MME, and implements wireless connection by using the S1-AP protocol.
  • S-GW Serving Gateway
  • MME Mainly responsible for all control plane functions of the user, that is, session management, including NAS signaling and security, tracking area management, P-GW and S-GW selection.
  • S-GW It is mainly responsible for data transmission, forwarding, and routing handover of the UE, and is used as a local mobility anchor point when the UE switches between eNBs. Among them, for each UE, only one S-GW serves it at a time.
  • P-GW An anchor point that is connected as a packet data network (English: Packet Data Network Gateway, PDN for short), responsible for IP address allocation of the UE, data packet filtering, rate control, and generation of charging information of the UE.
  • PDN Packet Data Network Gateway
  • HSS is a database for storing user subscription information.
  • the main functions of the device are storage user subscription information, user authentication, and location information management.
  • PCRF Used for QoS control, gating, and charging control based on service data flow.
  • SGSN Mainly completes the functions of routing and forwarding, mobility management, session management, logical link management, authentication and encryption, bill generation and output of packet data packets.
  • the service type of service data in NB-IoT is shown in Table 1.
  • the priority report has higher priority than the periodic report. It requires priority scheduling and transmission of exception reports. It is quasi-real-time and the delay is less than 10s. The periodic report is not sensitive to delay and can be delayed.
  • Some terminals send periodic reports or exception reports.
  • the network side cannot determine the type of data report according to the terminal. Only the terminal knows the type of data report it sends, so the network side cannot provide services for it. Therefore, in the present invention, The network side is notified by the terminal.
  • some terminals send a lower frequency of exception reports (such as smart water meters, smart meters, etc.), some terminals send a higher frequency of exception reports (such as smart parking, water pump control), provided by the embodiments of the present invention
  • the program can control the use of exception reports.
  • the downlink needs to distinguish the service priority, and preferentially schedule and transmit the high priority control commands.
  • Some users may have high-priority control commands, low-priority parameter configurations, and software upgrades. Some users have low-priority parameter configurations and software upgrades. Therefore, it is necessary to distinguish between different users. The priority of the business data.
  • the service priority can be differentiated according to the user type, and the service of the high priority user is a high priority service, and the service of the low priority user is a service of the low priority user. Low priority business.
  • the first information involved in the embodiment of the present invention includes at least one of a priority of the terminal service data and a service type of the service data; the second information includes a service type used by the terminal to request to transmit the service data, and/or Or priority.
  • the embodiment of the present invention provides a service data transmission method, where the mobility management entity receives the service data of the terminal through the NAS signaling message, and Acquiring the first information of the service, and then sending the service data and the first information to the gateway, so that the gateway can provide a charging service for the service data based on the first information, thereby controlling the high priority report of the terminal usage of.
  • the method includes:
  • the mobility management entity receives the NAS signaling message, where the NAS signaling message carries the service data of the terminal.
  • the mobility management entity acquires first information about the service data, where the first information includes at least one of a service type and a priority.
  • the service type may be a periodic report or an exception report
  • the priority may be the first priority or the second priority, where the first priority is higher than the second priority
  • the mobility management entity sends the service data and the first information to a gateway.
  • the gateway After receiving the service data and the first information, the gateway charges the service data based on the first information.
  • the foregoing access network device may be an eNB
  • the mobility management entity may be an MME
  • the gateway may be an S-GW or a P-GW, which is not limited herein.
  • the gateway, the access network device, and the mobility management entity in the embodiments of the present invention may be independent physical devices, software functional entities, or devices with the same functions, and are not limited.
  • the mobility management entity receives the service data of the terminal through the NAS signaling message, acquires the first information of the service, and then sends the service data and the first information to the gateway, so that the gateway can Business data provides billing services.
  • the terminal can be configured to configure the first information of the service data according to requirements when transmitting the service data, thereby avoiding low priority terminals, such as periodicity.
  • Report-based terminals smart water meters
  • exception reports This reduces data transmission congestion caused by the fact that most terminals use high priority or exception reports to transmit service data.
  • the traffic for the service data may be configured to be charged, or the number of data packets according to the service data may be charged, or the priority is based on the sending high priority or the service type.
  • the number of reported business data is billed.
  • different charging standards may be set according to priorities, and high-priority service data charges are higher than low-priority service data.
  • the service data of 10M traffic is also sent. If it is sent with high priority, it will charge RMB 1 yuan, and if it is sent with low priority, it will charge RMB 0.1 yuan.
  • the charging of the service data whose service type is the exception report is higher than the service data whose service type is the periodic report. For example, if the service data is sent once, if it is sent through the periodic report, the charge is 0.1 yuan, and if it is sent through the exception report, the charge is 0.5 yuan.
  • the mobile management entity receives the NAS signaling message in S201, which may be sent by the access network device or may be sent by the terminal.
  • the mobile management entity acquires the first information in step S202, which may be sent by the access network device, or may be sent by the terminal.
  • the mobility management entity receives the NAS signaling message sent by the access network device and the first information of the service data.
  • the mobility management entity receives the NAS signaling message sent by the terminal and the first information of the service data.
  • the mobility management entity receives the NAS signaling message sent by the access network device and the first information of the service data, where the NAS information message carries the service data of the terminal. See Figure 3.
  • the access network device determines first information of the service data to be sent by the terminal, where the first information includes at least one of a service type and a priority.
  • the access network device receives the service data that is sent by the terminal by using a NAS signaling message.
  • the access network device sends the service data and the first information to a mobility management entity.
  • the mobility management entity sends the service data and the first information to a gateway.
  • the gateway performs charging on the service data according to the first information.
  • the access network device is at the end of the receiving After the first information sent by the terminal, the foregoing method further includes:
  • S301a The access network device performs transmission resource management on the service data according to the first information.
  • performing transmission resource management on the service data based on the first information may be: allocating transmission resources, that is, network resources, to the service data to be sent based on the first information.
  • the service type of the service data to be transmitted by the terminal is an exception report, and the exception report has a requirement for the transmission delay. Therefore, the network resource allocated by the access network device for the service data needs to meet the delay requirement of the exception report. Further, the network resource allocated by the terminal in step S301a transmits the NAS signaling carrying the service data to the access network device.
  • the foregoing step S301 may specifically include: S3010a (as shown in FIG. 4) or S3010b-S3010g (as shown in FIG. 5).
  • the access network device receives the first information sent by the terminal.
  • the access network device receives a radio resource control (Radio Resource Control, RRC) connection establishment request message sent by the terminal, where the connection establishment request message carries the first information.
  • RRC Radio Resource Control
  • the access network device receives the second information sent by the terminal.
  • the second information may include a service type and/or a priority used by the terminal to request to transmit the service data.
  • the access network device receives the RRC connection setup request message sent by the terminal, where the connection establishment request message carries the second information.
  • the access network device sends the second information to a mobility management entity.
  • the mobility management entity receives the second information sent by the access network device, and authorizes the second information to obtain first service authorization information.
  • the mobile management entity obtains the first service authorization information for the second information according to the subscription information of the terminal when the second information that is sent by the access network device is authorized.
  • the first service authorization information may include indication information, where the indication information is used to indicate The second information is allowed or the second information is rejected.
  • the mobility management entity sends the first service authorization information to the access network device.
  • the access network device receives the first service authorization information sent by the mobility management entity, where the first service authorization information is used to indicate a service type and/or priority that is allowed to be used by the terminal to transmit the service data. level.
  • the access network device determines the first information according to the first service authorization information.
  • the first service authorization information may include indication information, where the indication information is used to indicate that the second information is allowed.
  • the first information includes at least one of a service type of the service data to be sent by the terminal and a priority of the service data.
  • the first service authorization information is to allow the second information
  • the first information determined by the access network device is the same as the second information
  • the first service authorization information is to reject the second information
  • the access is performed.
  • the first information determined by the network device is different from the second information. For example, if the service type of the second information is an exception report, if the first service authorization information is to allow the terminal to send the exception report, the service type of the second information determined by the access network device is an exception report, and if the first service authorization information is If the terminal sends the exception report, the second information determined by the access network device includes a service type that is a periodic report.
  • the mobility management entity authorizes the second information to obtain the first service authorization information
  • the mobility management entity authorizes the second information according to the subscription information of the terminal to obtain the first service authorization information.
  • the subscription information may include a priority of the service data that is allowed to be sent by the terminal or a service type of the service data.
  • the subscription information includes a service type that allows the service data sent by the terminal to be a periodic report. If the second information is an exception report, the mobility management entity authorizes the second information according to the subscription information to obtain the first service authorization information. Reject the second message.
  • the priority of the transmittable service data or the service type of the service data for each terminal by configuring the priority of the transmittable service data or the service type of the service data for each terminal, it is possible to prevent the low priority terminal (the terminal mainly based on periodic report, such as a smart water meter) from being used high. Priority reporting, so as to avoid data transmission congestion caused by high priority transmission service data for most terminals.
  • the subscription information may include a priority of the service data that is allowed to be sent by the terminal, and quota information corresponding to the priority, where the quota information corresponding to the priority is used to indicate that the sending is allowed in a specific time.
  • the number of priority business data The priority here is high priority.
  • the quantity can be the traffic of the business data or the number of times the business data is sent.
  • the network access device sends the service data according to the low priority, so that low-priority terminals (terminals with periodic reports, such as smart water meters) can be prevented from overusing high-priority reports, thereby avoiding the high priority of most terminals.
  • the transmission of data caused by the transmission of business data is congested.
  • the subscription information may include a service type of the service data of the service data that is allowed to be sent by the terminal, and quota information corresponding to the service type, where the quota information corresponding to the service type is used to indicate that the specific time is The number of business data that is allowed to send the service type.
  • the service type and the quota information of the service data of the service data that can be sent for each terminal if the service data of the service type that the terminal sends the exception type exceeds the quota information, the request is rejected.
  • the periodic report transmission it can avoid excessive use of exception reports by low-priority terminals (terminals with periodic reports, such as smart water meters), thereby reducing data transmission congestion caused by most terminals using exception reports to send service data. .
  • the access network device when the access network device receives the service type of the service data included in the second information sent by the terminal as an exception report, or the priority of the service data is a high priority, the access network device uses the service data.
  • the second information is sent to the mobility management entity for authorization. Therefore, before step S3010c, the method further includes: S3010cb, the access network device determines that the second information included in the terminal is received
  • the service type of the service data is an exception report or the priority is high priority.
  • the access network device may not authorize the second information by the mobility management entity. Instead, the second information is sent directly to the gateway to enable the mobility management entity to bill the service data.
  • the access network device is used as the base station, the terminal is called the UE, the mobility management entity is the MME, and the gateway includes the S-GW and the P-GW as an example.
  • the description is as follows:
  • the UE initiates an RRC connection setup request message to a base station (English: Base Station, BS for short).
  • a base station English: Base Station, BS for short.
  • the RRC establishment cause value indicates the first information.
  • the first information includes at least one of a priority of the service data and a service type of the service data.
  • the priority is taken as an example in this embodiment.
  • the priority includes a first priority and a second priority, wherein the first priority is higher than the second priority.
  • the base station allocates a transmission resource according to the RRC establishment cause value indicated by the UE.
  • the UE encapsulates the service data in the NAS signaling message and sends the message to the base station.
  • the NAS signaling message may be transmitted to the base station by using an RRC Connection Setup Complete message.
  • the terminal When transmitting the service data, the terminal transmits the service data to the base station through the transmission resource allocated by the base station.
  • the base station receives the NAS signaling message sent by the terminal, and sends the NAS signaling message and the priority corresponding to the service data to the MME.
  • the base station may send the service data and the priority of the service data to the MME by using an interface S1AP Initial UE message.
  • the MME After receiving the NAS signaling message and the priority of the service data, the MME obtains the service data from the NAS signaling message, and sends the priority of the service data and the service data to the S-GW.
  • the MME encapsulates the service data into a GPRS Tunneling Protocol (English: GPRS Tunnel Protocol User Plane, GTP-U) packet sent to the S-GW, where the GTP-U packet carries the packet header.
  • GTP-U GPRS Tunnel Protocol User Plane
  • the S-GW charges the service data according to the priority of the service data.
  • the S-GW may generate a charging data S-GW charging data record (English: Charging Data Record, CDR for short), and record the priority of the service data in the CDR.
  • the S-GW sends the priority of the service data and the service data to the P-GW.
  • the S-GW encapsulates the service data into the GTP-U data packet and sends the data to the S-GW, where the packet header of the GTP-U data packet carries the priority of the service data.
  • the P-GW charges the service data according to the priority of the service data.
  • the P-GW may generate a charging data P-GW CDR, and the priority of the service data is recorded in the CDR.
  • the terminal Before transmitting the service data, the terminal sends the priority of the service data to the base station, so after the base station receives the service data sent by the terminal, the MME sends the priority of the service data and the service data to the P-GW and the S-GW. Therefore, the P-GW and the S-GW perform charging control on the service data based on the priority of the service data, that is, the high-priority service data transmission and the low-priority service data transmission adopt different charging standards, and the base station transmits the service data.
  • the priority of the service data is sent to the P-GW and the S-GW, so that the P-GW and the S-GW provide the charging service for the service data according to the priority of the service data.
  • low-priority terminals intermediate terminals based on periodic reports
  • the access network device is an NB-IoT BS
  • the terminal is an NB-IoT UE
  • the mobility management entity is an MME
  • the gateway includes an S-GW and a P-GW.
  • the UE initiates an RRC connection setup request message to the base station.
  • the RRC establishment cause value in the RRC connection setup request message indicates the second information.
  • the second information includes the priority and/or service type that the UE requests to transmit the service data.
  • the service type can be an exception report or a periodic report, where the first priority is higher than the second priority.
  • the base station After receiving the RRC connection setup request message, the base station determines that the service type indicated by the RRC establishment cause value indicated by the UE is an exception report, and requests the MME to send an exception report authorization.
  • the MME determines first service authorization information for the second information of the service data according to the subscription information, where the first service authorization information is used to indicate a service type that is allowed to be used by the terminal to transmit the service data.
  • the subscription information may include a service type that allows the terminal to transmit service data that can be used by the service data. If the terminal does not allow the terminal to send the exception report, the first service authorization information indicates that the access network device periodically reports the transmission resource required for scheduling the service data. If the terminal allows the terminal to send the exception report, the service authorization information indicates the transmission resource required by the access network device to schedule the service data by using an exception report. That is, the service authorization information includes allowing the second information or rejecting the second information.
  • the subscription information may include an exception report used by the terminal to transmit the service data and quota information corresponding to the exception report, where the quota information is used to indicate that the service type is allowed to be an exception report within a specific time.
  • the amount of business data The quantity can be the traffic of the business data or the number of times the business data is sent.
  • the MME determines that the number of service data that the terminal needs to send is the exception report, the number of the service data does not exceed the quota information, the MME accepts the request, and instructs the access network device to schedule the transmission resource of the service data according to the exception report.
  • the MME may also send the third service authorization information to the access network device based on the subscription information, where the third service authorization information includes the quota information corresponding to the terminal exception report and the exception report, so that the access network device determines the third service authorization information.
  • the transmission resource is allocated for the service data to be sent by the terminal according to the exception report. Otherwise, the transmission resource is allocated for the service data to be sent by the terminal according to the periodic report.
  • the MME sends the first service authorization information to the base station.
  • the base station allocates, according to the first service authorization information, a transmission resource for transmitting, by the terminal, the service data.
  • the base station After receiving the service data sent by the terminal through the NAS signaling message, the base station forwards the service data to the MME, and notifies the MME that the service type of the service data is an exception report.
  • the MME After receiving the service data and the service type of the service data, the MME sends the service data and the service type of the service data to the S-GW.
  • the MME encapsulates the service data into a GPRS Tunneling Protocol (English: GPRS Tunnel Protocol User Plane, GTP-U) packet sent to the S-GW, where the GTP-U packet carries the packet header.
  • GTP-U GPRS Tunnel Protocol User Plane
  • the S-GW charges the service data according to the service type of the service data.
  • the S-GW can generate a charging data S-GW charging data record (English: Charging Data Decord, CDR for short), and record the service type of the service data in the CDR.
  • the S-GW sends the service data and the service type of the service data to the P-GW.
  • the S-GW encapsulates the service data into the GTP-U data packet and sends the service data to the S-GW, where the packet header of the GTP-U data packet carries the service type of the service data.
  • the P-GW charges the service data according to the service type of the service data.
  • the P-GW may generate a charging data P-GW CDR, and record the service type of the service data in the CDR.
  • the second implementation scenario of the first embodiment is described below, that is, the mobility management entity receives the NAS signaling message sent by the terminal.
  • the NAS information message carries the service data of the terminal and the first information of the service data. See Figure 8.
  • the mobility management entity receives the service data sent by the terminal through the NAS signaling message and the information of the service data, where the information of the service data includes at least one of a service type and a priority.
  • the mobility management entity sends the service data and the information of the service data to the gateway.
  • the gateway charges the service data according to the information of the service data.
  • the terminal passes the service data and the service data information through the NAS signaling message.
  • the mobile management entity sends the service data and the service data information to the gateway, so that the gateway performs charging processing on the service data according to the information of the service data.
  • the gateway performs charging processing on the service data according to the information of the service data.
  • the access network device is a base station
  • the terminal is a UE
  • the mobility management entity includes an MME
  • the gateway includes an S-GW and a P-GW.
  • the access network device receives an RRC connection setup complete message sent by the terminal, where the message carries a NAS signaling message including service data and information of the service data.
  • the access network device forwards the received NAS signaling message to the MME.
  • the MME obtains service data and information of the service data from the NAS signaling message sent by the terminal.
  • the information of the service data includes at least one of a service type of the service data and a priority of the service data.
  • the priority of the information of the service data including the service data is taken as an example.
  • the MME After obtaining the priority of the service data and the service data, the MME sends the priority of the service data and the service data to the S-GW.
  • the MME encapsulates the service data into the GTP-U data packet and sends the data to the S-GW, where the packet header of the GTP-U data packet carries the priority of the service data.
  • the S-GW charges the service data according to the priority of the service data.
  • the S-GW may generate a charging data S-GW CDR, and the priority of the service data is recorded in the CDR.
  • the S-GW sends the priority of the service data and the service data to the P-GW.
  • the S-GW encapsulates the service data into the GTP-U data packet and sends the data to the S-GW, where the packet header of the GTP-U data packet carries the priority of the service data.
  • the P-GW charges the service data according to the priority of the service data.
  • the P-GW may generate a charging data P-GW CDR, and the priority of the service data is recorded in the CDR.
  • the embodiment of the present invention provides a service data transmission method, where the network side sends the second service authorization information of the terminal to the terminal, and the second service authorization information is used to indicate the permission The service type and/or priority of the service data used by the terminal to transmit the service data, so that the terminal determines the information of the sent service data based on the second service authorization information, where the information of the service data includes the service type of the service data. And at least one of the priorities of the service data, and notifying the information of the service data to the base station, so that the base station provides service for transmitting the service data based on the information of the service data.
  • the method includes:
  • the terminal sends a request message to the mobility management entity, where the request message includes the transmission mode indication information, where the transmission mode indication information is used to indicate that the terminal uses the non-access stratum NAS signaling message to transmit the service data.
  • the mobility management entity receives the request message sent by a terminal.
  • the mobility management entity determines, according to the request message, that the terminal transmits the service data by using a non-access stratum NAS signaling message, the mobility management entity determines the terminal according to the subscription information of the terminal. Second business authorization information.
  • the second service authorization information includes information indicating a service type and/or priority that the terminal is allowed to transmit service data.
  • the mobility management entity sends the second service authorization information to the terminal.
  • the terminal receives the second service authorization information sent by the mobility management entity.
  • S1006 The terminal determines information about the service data according to the second service authorization information.
  • the information of the service data includes at least one of a service type of the service data and a priority of the service data.
  • S1007 The terminal sends the information about the service data to the access network device.
  • the mobility management entity acquires the subscription information of the terminal from the HSS.
  • the subscription information may include a priority of the service data that is allowed to be sent by the terminal and/or a service type of the service data.
  • the mobility management entity will allow the priority and/or industry of the service data sent by the terminal. Transmitting the second service authorization information to the terminal, so that the terminal determines the service type and/or priority of the service data that is allowed to be sent, so that when the service data requested by the application layer is received, the second service is
  • the authorization information sets the priority of the service data and/or the service type of the service data, and prevents the low priority terminal from transmitting the service data with a high priority; or
  • the subscription information may include a priority of the service data that is allowed to be sent by the terminal, and second quota information, where the second quota information is used to indicate the number of service data that is allowed to be sent in the specific time.
  • the priority here is high priority.
  • the quantity can be the traffic of the business data or the number of times the business data is sent.
  • the mobility management entity sends the priority of the service data sent by the terminal and the second quota information to generate the second service authorization information, so that the terminal determines that the number of the high priority service data that is sent does not reach the second quota information, The service data is sent with a high priority.
  • the service data can only be sent with a low priority, thereby preventing the low-priority terminal from overusing the high-priority transmission service.
  • the subscription information may include a service type that allows the service data sent by the terminal to be an exception report and first quota information, where the quota information is used to indicate the number of service data that is allowed to send the service type as an exception report within a specific time.
  • the mobility management entity sends the service type of the service data that is sent by the terminal and the second service authorization information to the terminal, so that the terminal determines that the number of service data sent by the terminal is the first quota information.
  • the service data can be sent by using the exception report. If the terminal determines that the number of service data sent by the exception type is the second quota information, the service data can only be sent by the periodic report, thereby avoiding the low priority terminal.
  • Sexual reporting-based terminals) over-use high-priority to send business data.
  • the second embodiment is specifically described below by taking the EPS system as an example, as shown in FIG.
  • the access network device is a base station
  • the terminal is called a UE
  • the mobility management entity is an MME
  • the gateway includes an S-GW and a P-GW.
  • the UE sends a request message to the mobility management entity, where the request message includes transmission mode indication information, where the transmission mode indication information is used to indicate that the terminal uses the non-access stratum NAS signaling message to transmit service data.
  • the transmitting party When a specific UE initiates an attach request (Attach Request), the transmitting party will transmit The type indication information is sent to the mobility management entity.
  • the MME After receiving the request message, the MME obtains the subscription information of the UE from the HSS, and determines the second service authorization information based on the subscription information.
  • the second service authorization information includes information indicating a service type and/or a priority used to allow the terminal to transmit service data, and the second service authorization information may further include first quota information, the first The quota information is used to indicate the amount of service data that is allowed to transmit the service type within a certain time.
  • the second service authorization information may further include second quota information, where the quota information is used to indicate the number of service data that is allowed to send the priority in a specific time.
  • the UE determines whether the UE can transmit high priority service data or send an exception report, and the number of allowed transmissions.
  • S1103 The MME notifies the UE of the second service authorization information by using an Attach Accept message.
  • the UE determines the information of the service data based on the second service authorization information.
  • the information of the service data includes at least one of a service type of the service data and a priority of the service data.
  • the service data may be sent with a high priority.
  • the service data is sent with a low priority.
  • the UE initiates an RRC connection setup request message to the base station, and sets an RRC connection establishment cause value based on the determined information of the service data.
  • S1106 The base station allocates a transmission resource according to the RRC establishment cause value to the UE transmission service data.
  • the UE transmits the service data to the base station through the NAS signaling message based on the transmission resource allocated by the base station.
  • the base station After receiving the service data sent by the UE, the base station forwards the service data to the MME, and notifies the MME of the service data.
  • the MME After receiving the service data and the information of the service data, the MME sends the service data and the information of the service data to the S-GW.
  • the MME encapsulates the service data into a GPRS Tunneling Protocol (English: GPRS Tunnel Protocol User Plane, GTP-U) packet sent to the S-GW, where the GTP-U packet carries the packet header.
  • GTP-U GPRS Tunnel Protocol User Plane
  • the S-GW charges the service data according to the information of the service data.
  • the S-GW may generate a charging data S-GW charging data record CDR, and record information of the service data in the CDR.
  • the S-GW sends the service data and the information of the service data to the P-GW.
  • the S-GW encapsulates the service data into the GTP-U data packet and sends the information to the S-GW, where the packet header of the GTP-U data packet carries the information of the service data.
  • the P-GW charges the service data according to the information of the service data.
  • the P-GW may generate a charging data P-GW CDR, and record QoS information of the service data in the CDR.
  • the MME when the MME determines that the terminal uses the non-access stratum NAS signaling message to transmit the service data, the MME sends the second service authorization information of the terminal to the terminal, so that the terminal determines the sent service data based on the second service authorization information. And transmitting the information of the service data to the base station, so that the base station provides service for transmitting the service data based on the information of the service data.
  • the base station transmits the information of the service data to the P-GW and the S-GW, so that the P-GW and the S-GW charge the service data based on the information of the service data.
  • high-priority service data transmission and low-priority service data transmission adopt different charging standards, which prevents low-priority terminals (intermediate terminals mainly based on periodic reports) from being excessively transmitted through high priority.
  • Service data thereby reducing data transmission congestion caused by the high priority transmission service data of most terminals.
  • the embodiment of the present invention provides a service data transmission method, where the mobility management entity provides downlink service data information to the access network device, and the service data information includes the priority of the service data. And/or the service type of the service data, so that the access network device performs transmission resource management on the service data based on the information of the service data.
  • the method includes:
  • the mobility management entity receives the service data of the terminal sent by the gateway.
  • the mobility management entity is an MME in the EPS system
  • the gateway is an S-GW or a P-GW.
  • the mobility management entity acquires first information of the service data, where the first information includes at least one of a service type and a priority.
  • the mobility management entity sends a NAS signaling message to the access network device, where the NAS signaling message carries the service data.
  • the mobility management entity sends the service data and the first information of the service data to the access network device.
  • the access network device After receiving the first information of the service data, the access network device performs transmission resource management on the service data based on the first information of the service data.
  • performing transmission resource management on the service data based on the first information may be: allocating transmission resources, that is, network resources, to the service data to be sent based on the first information.
  • the service type of the service data to be transmitted by the terminal is an exception report, and the exception report has a requirement for the transmission delay. Therefore, the network resource allocated by the access network device for the service data needs to meet the delay requirement of the exception report.
  • the first information that the mobility management entity acquires the service data may be implemented by:
  • the mobility management entity determines first information of the service data according to the subscription information of the terminal.
  • the subscription information may include a priority of the service data that is allowed to be sent by the terminal and/or a service type of the service data. For example, if the service type of the service data that is allowed to be sent by the terminal is a periodic report, the mobility management entity determines that the service type of the service data included in the first information is a periodic report; or if the subscription information includes The service type of the service data that is allowed to be sent by the terminal is an exception report, and the mobility management entity determines that the service type of the service data included in the first information is an exception report.
  • Carrying the first information of the service data in a packet header of a data packet of the service data then moving The dynamic management entity acquires the first information of the service data from a header of the data packet of the service data.
  • the gateway may obtain the first information of the service data from the carried DSCP (IPv4) or ToS (IPv6) of the service data.
  • IPv4 carried DSCP
  • IPv6 ToS
  • the access network device is an eNB in the EPS system
  • the gateway is a P-GW or an S-GW in the EPS system
  • the mobility management entity is an MME in the EPS system.
  • the P-GW sends the service data of the terminal to the S-GW.
  • the S-GW After receiving the service data, the S-GW sends the service data to the MME.
  • the MME After receiving the service data, the MME acquires the first information of the service data from the HSS.
  • the MME may also obtain the first information of the service data from the packet header of the data packet of the service data.
  • the first information takes the priority of the service data as an example.
  • the packet header of the service data packet carries a differential service code point (English: Differentiated Services Code Point, DSCP for short) or a service type (English: Type of Service, for short: ToS), and the first information is included in the DSCP or the ToS.
  • DSCP Differentiated Services Code Point
  • ToS Type of Service
  • S1304 The MME sends the priority of the service data and the service data to the base station.
  • the MME determines the priority of the service data to generate an ARP or other priority parameter, and sends the service data and the corresponding priority parameter in the Downlink NAS Transport message to the base station when transmitting the downlink NAS transport message.
  • the base station After receiving the priority of the service data and the service data, the base station performs transmission resource management on the service data based on the priority of the service data.
  • the base station allocates network resources to the service data based on the priority of the service data, so that the base station sends the service data to the terminal by using the allocated network resources.
  • An embodiment of the present invention further provides an access network device.
  • the access network device includes:
  • a determining unit 1401 configured to determine first information of service data to be sent by the terminal, where the first information includes at least one of a service type and a priority;
  • the receiving unit 1402 is configured to receive the service data that is sent by the terminal by using a non-access stratum NAS signaling message;
  • the sending unit 1403 is configured to send the service data received by the receiving unit 1402 and the first information determined by the determining unit 1401 to a gateway, so that the gateway performs the foregoing according to the first information.
  • Business data is billed.
  • the access network device may further include: a management unit 1404, after the determining unit 1401 determines the first information of the service data to be sent by the terminal, the receiving unit 1402 receives the Before the terminal passes the service data sent by the non-access stratum NAS signaling message, the terminal performs transmission resource management on the service data according to the first information.
  • a management unit 1404 after the determining unit 1401 determines the first information of the service data to be sent by the terminal, the receiving unit 1402 receives the Before the terminal passes the service data sent by the non-access stratum NAS signaling message, the terminal performs transmission resource management on the service data according to the first information.
  • the determining unit 1401 is specifically configured to: when the receiving unit 1402 receives the first information sent by the terminal, determine the first information.
  • the receiving unit 1402 is further configured to receive second information sent by the terminal, where the second information includes a service type used by the terminal to request to transmit the service data, and/or priority;
  • the sending unit 1403 is further configured to send the second information to the mobility management entity
  • the receiving unit 1402 is further configured to receive the first service authorization information sent by the mobility management entity, where the first service authorization information is used to indicate a service type and/or a service type used by the terminal to transmit the service data. priority;
  • the determining unit 1401 is specifically configured to determine the first information according to the first service authorization information.
  • the first service authorization information includes indication information, and the indication information is used to indicate that the second information is allowed.
  • each functional unit in each embodiment of the present invention may be integrated into one processing. In the device, it can be physically alone or two or two.
  • the above units are integrated in one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software function module.
  • the receiver 1501, the processor 1502, and the communication interface 1503 may be included.
  • a memory 1504 is also included.
  • the memory 1504 is configured to store program code executed by the processor 1502.
  • the physical hardware corresponding to the sending unit 1403 may be the communication interface 1503, the physical hardware corresponding to the receiving unit 1402 may be the receiver 1501, and the physical hardware corresponding to the determining unit 1401 and the management unit 1404 may be the processor 1502.
  • the processor 1502 can be a central processing unit (English: central processing unit, CPU for short), or a digital processing unit or the like.
  • the processor 1502 receives the message sent by the terminal through the receiver 1501 and transmits and receives a message to and from the gateway and the mobility management entity through the communication interface 1503.
  • the specific connection medium between the receiver 1501, the processor 1502, the communication interface 1503, and the memory 1504 is not limited in the embodiment of the present invention.
  • the receiver 1501, the processor 1502, the communication interface 1503, and the memory 1504 are connected by a bus 1505 in FIG. 15.
  • the bus is indicated by a thick line in FIG. 15, and the connection manner between other components is only Schematic descriptions are not limited.
  • the bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 15, but it does not mean that there is only one bus or one type of bus.
  • the memory 1504 may be a volatile memory (English: volatile memory), such as random access memory (English: random-access memory, abbreviation: RAM); the memory 1504 may also be a non-volatile memory (English: non-volatile memory) For example, read-only memory (English: read-only memory, abbreviation: ROM), flash memory (English: flash memory), hard disk (English: hard disk drive, abbreviation: HDD) or solid state drive (English: solid-state drive Abbreviation: SSD), or memory 1504 is any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited thereto.
  • the memory 1504 may be a combination of the above memories.
  • the processor 1502 is configured to determine first information of service data to be sent by the terminal, where the first information is Information includes at least one of a service type and a priority;
  • the receiver 1501 is configured to receive the service data that is sent by the terminal by using a non-access stratum NAS signaling message.
  • the communication interface 1503 is configured to send the service data and the first information to the gateway, so that the gateway charges the service data according to the first information.
  • the receiver 1501 receives the service data sent by the terminal through the NAS signaling message, the processor 1502 is further configured to perform transmission resource management on the service data according to the first information.
  • the receiver 1501 is further configured to receive the first information sent by the terminal.
  • the receiver 1501 is further configured to receive second information sent by the terminal, where the second information includes a service type used by the terminal to request to transmit the service data, and/or priority;
  • the communication interface 1503 is further configured to send the second information to the mobility management entity
  • the communication interface 1503 is further configured to receive first service authorization information sent by the mobility management entity, where the first service authorization information is used to indicate a service type and/or a service type used by the terminal to transmit the service data. priority;
  • the processor 1502 is specifically configured to determine the first information according to the first service authorization information.
  • the first service authorization information includes indication information, and the indication information is used to indicate that the second information is allowed.
  • the access network device in the embodiment shown in FIG. 14 or FIG. 15 may be used to perform the operation steps of the access network device or the base station in the implementation scenarios of the first embodiment or the first embodiment. A narrative.
  • the embodiment of the present invention provides a mobility management entity.
  • the mobility management entity includes:
  • the receiving unit 1601 is configured to receive a non-access stratum NAS signaling message, where the NAS signaling message carries service data of the terminal;
  • the acquiring unit 1602 is configured to acquire first information of the service data received by the receiving unit 1601, where the first information includes at least one of a service type and a priority;
  • the sending unit 1603 is configured to send the service data and the first information to the gateway, so that the gateway performs charging on the service data.
  • the obtaining unit 1602 is configured to acquire the first information when the receiving unit 1601 receives the first information sent by the access network device.
  • the receiving unit 1601 before receiving the first information sent by the access network device, is further configured to receive second information sent by the access network device, where the second The information includes a service type and/or a priority used by the terminal to request to transmit the service data;
  • the mobility management entity further includes an authorization unit 1604, configured to authorize the second information according to the subscription information of the terminal to obtain first service authorization information, where the first service authorization information is used to indicate that the terminal is allowed to be The type of service and/or priority used to transmit the service data;
  • the sending unit 1603 is further configured to send the first service authorization information to the access network device, so that the access network device determines the first information based on the first service authorization information.
  • the obtaining unit 1602 is specifically configured to acquire the first information when the receiving unit 1601 receives the first information sent by the terminal.
  • each functional unit in each embodiment of the present invention may be integrated into one processing. In the device, it may be physically present alone, or two or more units may be integrated in one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software function module.
  • a communication interface 1701, a processor 1702, and a memory 1703 may be included.
  • the memory 1703 is configured to store program code executed by the processor 1702.
  • the physical hardware corresponding to the sending unit 1603 may be the communication interface 1701, and the physical hardware corresponding to the receiving unit 1601 may be the communication interface 1701, and the acquiring unit 1602 and the physical hardware corresponding to the authorization unit 1604 may be the processor 1702.
  • the processor 1702 can be a central processing unit (English: central processing unit, CPU for short), or a digital processing unit or the like.
  • the processor 1702 receives and transmits a message through the communication interface 1701.
  • connection medium between the communication interface 1701, the processor 1702, and the memory 1703 is not limited in the embodiment of the present invention.
  • the communication interface 1701, the processor 1702, and the memory 1703 are connected by a bus 1704 in FIG. 17, and the bus is indicated by a thick line in FIG. 17, and the connection manner between other components is only schematically illustrated. , not limited to.
  • the bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 17, but it does not mean that there is only one bus or one type of bus.
  • the memory 1703 may be a volatile memory such as a RAM; the memory 1703 may also be a non-volatile memory such as a ROM, a flash memory, an HDD, an SSD, or the memory 1703 is capable of carrying or storing a desired program in the form of an instruction or data structure. Code and any other medium that can be accessed by a computer, but is not limited thereto.
  • the memory 1703 may be a combination of the above memories.
  • a communication interface 1701 configured to receive a non-access stratum NAS signaling message, where the NAS signaling message carries service data of the terminal;
  • the processor 1702 is configured to acquire first information of the service data, where the first information includes at least one of a service type of the service data and a priority of the service data;
  • the communication interface 1701 is configured to send the service data and the first information to a gateway, so that the gateway performs charging on the service data.
  • the communication interface 1701 is further configured to receive the first information sent by the access network device.
  • the communication interface 1701 is further configured to receive second information sent by the access network device before receiving the first information sent by the access network device, where
  • the second information includes a service type and/or a priority used by the terminal to request to transmit the service data;
  • the processor 1702 is further configured to: feed the second information according to the subscription information of the terminal.
  • the first authorization authorization information is used to indicate the service type and/or priority used by the terminal to transmit the service data.
  • the communication interface 1701 is further configured to send the first service authorization information to the access network device, so that the access network device determines the first information based on the first service authorization information.
  • the communication interface 1701 is further configured to receive the first information sent by the terminal.
  • the mobility management entity in the embodiment shown in FIG. 16 or 17 may be used to perform the operation steps of the mobility management entity or the MME in the implementation scenarios of the first embodiment or the first embodiment, and details are not described herein.
  • the embodiment of the invention further provides a gateway.
  • the gateway includes:
  • the receiving unit 1801 is configured to receive service data of the terminal sent by the mobility management entity and first information of the service data, where the first information includes at least one of a service type and a priority;
  • the charging unit 1802 is configured to perform charging on the service data according to the first information received by the receiving unit 1801.
  • each functional unit in each embodiment of the present invention may be integrated into one processing. In the device, it may be physically present alone, or two or more units may be integrated in one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software function module.
  • a communication interface 1901, a processor 1902, and a memory 1903 may be included.
  • the memory 1903 is configured to store program code executed by the processor 1902.
  • the physical hardware corresponding to the receiving unit 1801 may be the communication interface 1901, and the physical hardware corresponding to the charging unit 1802 may be the processor 1902.
  • the processor 1902 can be a central processing unit (English: central processing unit, CPU for short), or a digital processing unit or the like.
  • the processor 1902 receives and transmits a message through the communication interface 1901.
  • the communication interface 1901, the processor 1902, and the memory 1903 are not limited in the embodiment of the present invention.
  • the communication interface 1901, the processor 1902, and the memory 1903 are connected by a bus 1904 in FIG. 19.
  • the bus is indicated by a thick line in FIG. 19, and the connection manner between other components is only schematically illustrated. , not limited to.
  • the bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 19, but it does not mean that there is only one bus or one type of bus.
  • the memory 1903 may be a volatile memory such as a RAM; the memory 1903 may also be a non-volatile memory such as a ROM, a flash memory, an HDD, an SSD, or the memory 1903 is capable of carrying or storing a desired program in the form of an instruction or data structure. Code and any other medium that can be accessed by a computer, but is not limited thereto.
  • the memory 1903 may be a combination of the above memories.
  • the communication interface 1901 is configured to receive service data of the terminal sent by the mobility management entity and first information of the service data, where the first information includes at least one of a service type and a priority;
  • the processor 1902 is configured to perform charging on the service data according to the first information received by the communication interface 1901.
  • the gateway in the embodiment shown in FIG. 18 or 19 may be used to perform the operation steps of the gateway or the S-GW or the P-GW in the implementation scenarios of the first embodiment or the first embodiment. A narrative.
  • An embodiment of the present invention further provides another access network device.
  • the access network device includes:
  • the receiving unit 2001 is configured to receive service data that is sent by the mobility management entity by using a non-access stratum NAS signaling message, and receive information about the service data sent by the mobility management entity, where the information of the service data includes the service At least one of a service type of data and a priority of the business data;
  • the management unit 2002 is configured to perform transmission resource management on the service data according to the information of the service data received by the receiving unit 2001.
  • the division of the unit in the embodiment of the present invention is schematic, and is only a logical function division. In actual implementation, there may be another division manner, and in addition, various functions in various embodiments of the present invention. Units can be integrated into one processor, or they can exist physically alone, or two or more units can be integrated into one unit. The above integrated unit can be implemented in the form of hardware or in the form of a software function module.
  • a communication interface 2101 and a processor 2102 may be included.
  • a memory 2103 is also included.
  • the memory 2103 is configured to store program code executed by the processor 2102.
  • the physical hardware corresponding to the receiving unit 2001 may be the communication interface 2101, and the physical hardware corresponding to the management unit 2002 may be the processor 2102.
  • the communication interface 2101 is for transmitting data or a message to the terminal.
  • the processor 2102 can be a CPU, or a digital processing unit or the like.
  • the processor 2102 receives and transmits messages via the communication interface 2101.
  • connection medium between the communication interface 2101, the processor 2102, and the memory 2103 is not limited in the embodiment of the present invention.
  • the communication interface 2101, the processor 2102, and the memory 2103 are connected by a bus 2104 in FIG. 21, and the bus is indicated by a thick line in FIG. 21, and the connection manner between other components is only illustrative.
  • the description is not limited.
  • the bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in FIG. 21, but it does not mean that there is only one bus or one type of bus.
  • the memory 2103 may be a volatile memory such as a RAM; the memory 2103 may also be a non-volatile memory such as a ROM, a flash memory, an HDD, an SSD, or the memory 2103 is a program capable of carrying or storing a desired program in the form of an instruction or data structure. Code and any other medium that can be accessed by a computer, but is not limited thereto.
  • the memory 2103 may be a combination of the above memories.
  • the communication interface 2101 is configured to receive service data that is sent by the mobility management entity by using a non-access stratum NAS signaling message, and receive information about the service data sent by the mobility management entity, where the information of the service data includes the service At least one of a service type of the data and a priority of the service data; the processor 2102 is configured to perform transmission resource management on the service data according to the information of the service data.
  • the access network device in the embodiment shown in FIG. 20 or 21 can be used for execution.
  • the operation steps of the access network device or the base station in the implementation scenarios of the third embodiment or the third embodiment are not described again.
  • the embodiment of the present invention provides a mobility management entity. As shown in FIG. 22, the mobility management entity includes:
  • the receiving unit 2201 is configured to receive service data of the terminal sent by the gateway.
  • the acquiring unit 2202 is configured to acquire first information of the service data received by the receiving unit 2202, where the first information includes at least one of a service type of the service data and a priority of the service data. ;
  • the sending unit 2203 is configured to send, by the access network device, a non-access stratum NAS signaling message, where the NAS signaling message carries the service data acquired by the acquiring unit 2202, and sends the first information to the
  • the access network device is configured to enable the access network device to perform transmission resource management on the service data according to the first information.
  • the obtaining unit 2202 is specifically configured to determine the first information according to the subscription information of the terminal; or
  • the first information is carried in a packet header of the data packet of the service data, and the acquiring unit 2202 acquires the first information from a packet header of the data packet of the service data.
  • each functional unit in each embodiment of the present invention may be integrated into one processing. In the device, it may be physically present alone, or two or more units may be integrated in one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software function module.
  • a communication interface 2301, a processor 2302, and a memory 2303 may be included.
  • the memory 2303 is configured to store program code executed by the processor 2302.
  • the physical hardware corresponding to the receiving unit 2201 may be the communication interface 2301, and the physical hardware corresponding to the obtaining unit 2202 may be the processor 2302.
  • the physical hardware corresponding to the sending unit 2203 may be the communication interface 2301.
  • the processor 2302 can be a CPU, or a digital processing unit or the like. Processor 2302 The message is received and transmitted via the communication interface 2301.
  • connection medium between the communication interface 2301, the processor 2302, and the memory 2303 is not limited in the embodiment of the present invention.
  • the communication interface 2301, the processor 2302, and the memory 2303 are connected by a bus 2304 in FIG. 23.
  • the bus is indicated by a thick line in FIG. 23, and the connection manner between other components is only schematically illustrated. , not limited to.
  • the bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in FIG. 23, but it does not mean that there is only one bus or one type of bus.
  • the memory 2303 can be a volatile memory such as a RAM; the memory 2303 can also be a non-volatile memory such as a ROM, a flash memory, an HDD, an SSD, or the memory 2303 can be used to carry or store a desired program in the form of an instruction or data structure. Code and any other medium that can be accessed by a computer, but is not limited thereto.
  • the memory 2303 can be a combination of the above memories.
  • the communication interface 2301 is configured to receive service data of the terminal sent by the gateway.
  • the processor 2302 is configured to acquire first information of the service data, where the first information includes at least one of a service type of the service data and a priority of the service data.
  • the communication interface 2301 is configured to send a non-access stratum NAS signaling message to the access network device, where the NAS signaling message carries the service data, and send the first information to the access network device to And causing the access network device to perform transmission resource management on the service data according to the first information.
  • the processor 2302 is specifically configured to determine the first information according to the subscription information of the terminal; or
  • the first information is carried in a packet header of the data packet of the service data, and the processor 2302 is specifically configured to obtain the first information from a packet header of the data packet of the service data.
  • the mobility management entity in the embodiment shown in FIG. 22 or FIG. 23 may be used to perform the operation steps of the mobility management entity or the MME in each implementation scenario of the foregoing method embodiment 3 or the third embodiment, and details are not described herein.
  • the embodiment of the present invention provides a mobility management entity.
  • the mobility management entity includes:
  • the receiving unit 2401 is configured to receive a request message, where the request message includes transmission mode indication information, where the transmission mode indication information is used to indicate that the terminal uses the non-access stratum NAS signaling message to transmit service data.
  • a determining unit 2402 configured to determine, according to the request message, that the terminal transmits the service data by using a non-access stratum NAS signaling message, and determining, according to the subscription information of the terminal, the second service authorization information of the terminal.
  • the second service authorization information includes information indicating a service type and/or a priority used by the terminal to allow the service data to be transmitted;
  • the sending unit 2403 is configured to send the second service authorization information determined by the determining unit 2402 to the terminal.
  • the second service authorization information further includes first quota information, where the first quota information is used to indicate that the number of service data of the service type is allowed to be sent within a specific time.
  • the service authorization information further includes second quota information, where the second quota information is used to indicate the quantity of the priority service data that is allowed to be sent in a specific time.
  • each functional unit in each embodiment of the present invention may be integrated into one processing. In the device, it may be physically present alone, or two or more units may be integrated in one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software function module.
  • a communication interface 2501, a processor 2502, and a memory 2503 may be included.
  • the memory 2503 is configured to store program code executed by the processor 2502.
  • the physical hardware corresponding to the receiving unit 2401 may be the communication interface 2501, and the physical hardware corresponding to the determining unit 2402 may be the processor 2502.
  • the physical hardware corresponding to the sending unit 2403 may be the communication interface 2501.
  • the processor 2502 can be a CPU, or a digital processing unit or the like.
  • the processor 2502 receives the message through the communication interface 2501 and transmits the message through the communication interface 2501.
  • connection medium between the communication interface 2501, the processor 2502, and the memory 2503 is not limited in the embodiment of the present invention.
  • the communication interface 2501, the processor 2502, and the memory 2503 are connected by a bus 2504 in FIG. 25.
  • the bus is indicated by a thick line in FIG. 25, and the connection manner between other components is only schematically illustrated. , not limited to.
  • the bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 25, but it does not mean that there is only one bus or one type of bus.
  • the memory 2503 may be a volatile memory such as a RAM; the memory 2503 may also be a non-volatile memory such as a ROM, a flash memory, an HDD, an SSD, or the memory 2503 is capable of carrying or storing a desired program in the form of an instruction or a data structure. Code and any other medium that can be accessed by a computer, but is not limited thereto.
  • the memory 2503 may be a combination of the above memories.
  • the communication interface 2501 is configured to receive a request message, where the request message includes transmission mode indication information, where the transmission mode indication information is used to indicate that the terminal uses the non-access stratum NAS signaling message to transmit service data.
  • the processor 2502 is configured to: when determining, according to the request message, that the terminal transmits the service data by using a non-access stratum NAS signaling message, determining, according to the subscription information of the terminal, the second service authorization of the terminal Information, the second service authorization information includes information indicating a service type and/or a priority used to allow the terminal to transmit service data;
  • the communication interface 2501 is further configured to send the second service authorization information to the terminal.
  • the second service authorization information further includes first quota information, where the first quota information is used to indicate that the number of service data of the service type is allowed to be sent within a specific time.
  • the service authorization information further includes second quota information, where the second quota information is used to indicate the quantity of the priority service data that is allowed to be sent in a specific time.
  • the mobility management entity in the embodiment shown in FIG. 24 or 25 may be used to perform the operation steps of the mobility management entity or the MME in the implementation scenarios of the foregoing method embodiment 2 or the second embodiment, and details are not described herein.
  • the embodiment of the invention provides a terminal. As shown in FIG. 26, the terminal includes:
  • the sending unit 2601 is configured to send a request message to the mobility management entity, where the request message includes transmission mode indication information, where the transmission mode indication information is used to indicate that the terminal uses the non-access stratum NAS signaling message to transmit service data.
  • the receiving unit 2602 is configured to receive second service authorization information sent by the mobility management entity, where the second service authorization information includes information indicating a service type and/or priority used by the terminal to transmit service data. ;
  • a determining unit 2603 configured to determine, according to the second service authorization information received by the receiving unit 2602, information of the service data, where the information of the service data includes a service type of the service data and the service data. At least one of the priorities;
  • the sending unit 2601 is further configured to send information about the service data determined by the determining unit 2603 to the access network device.
  • the second service authorization information further includes first quota information, where the first quota information is used to indicate the number of service data that is allowed to be sent in the specific time.
  • the second service authorization information further includes second quota information, where the quota information is used to indicate the number of service data that is allowed to send the priority in a specific time.
  • each functional unit in each embodiment of the present invention may be integrated into one processing. In the device, it may be physically present alone, or two or more units may be integrated in one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software function module.
  • the receiver 2701, the processor 2702, and the transmitter 2703 may be included.
  • a memory 2704 is also included.
  • the memory 2704 configured to store program code executed by the processor 2702.
  • the physical hardware corresponding to the receiving unit 2602 may be the receiver 2701, and the physical hardware corresponding to the determining unit 2603 may be the processor 2702.
  • the physical hardware corresponding to the sending unit 2601 may be the transmitter 2703.
  • the processor 2702 can be a CPU, or a digital processing unit or the like.
  • the processor 2702 receives the message through the receiver 2701 and transmits the message through the transmitter 2703.
  • the specific connection medium between the receiver 2701, the processor 2702, the transmitter 2703, and the memory 2704 is not limited in the embodiment of the present invention.
  • the receiver 2701, the processor 2702, the transmitter 2703, and the memory 2704 are connected by a bus 2705 in FIG. 27.
  • the bus is indicated by a thick line in FIG. 27, and the connection manner between other components is only Schematic descriptions are not limited.
  • the bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 27, but it does not mean that there is only one bus or one type of bus.
  • the memory 2704 can be a volatile memory, such as a RAM; the memory 2704 can also be a non-volatile memory, such as a ROM, flash memory, HDD, SSD, or the memory 2704 can be used to carry or store a desired program in the form of an instruction or data structure. Code and any other medium that can be accessed by a computer, but is not limited thereto. Memory 2704 can be a combination of the above memories.
  • the transmitter 2703 is configured to send a request message to the mobility management entity, where the request message includes transmission mode indication information, where the transmission mode indication information is used to indicate that the terminal uses the non-access stratum NAS signaling message to transmit service data.
  • the receiver 2701 is configured to receive second service authorization information sent by the mobility management entity, where the second service authorization information includes information indicating a service type and/or priority used by the terminal to transmit service data. ;
  • the processor 2702 is configured to determine information about the service data according to the second service authorization information, where the information of the service data includes at least one of a service type of the service data and a priority of the service data. ;
  • the transmitter 2703 is further configured to send information about the service data to the access network device.
  • the second service authorization information further includes first quota information, where The first quota information is used to indicate the number of service data that is allowed to send the service type within a certain time.
  • the second service authorization information further includes second quota information, where the quota information is used to indicate the number of service data that is allowed to send the priority in a specific time.
  • the terminal in the embodiment shown in FIG. 26 or 27 may be used to perform the operation steps of the terminal or the UE in the implementation scenarios of the foregoing method embodiment 2 or the second embodiment, and details are not described herein.
  • embodiments of the present invention can be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware. Moreover, the invention can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.
  • computer-usable storage media including but not limited to disk storage, CD-ROM, optical storage, etc.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in a block or blocks of a flow or a flow and/or a block diagram of a flowchart Step.

Landscapes

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

Abstract

一种业务数据传输方法及设备，用以解决现有技术中存在的网络侧无法为不同类型的NB-IoT业务提供针对性服务的问题。该方法包括：接入网设备确定终端待发送的业务数据的第一信息，所述第一信息包括业务类型和优先级中的至少一种；然后所述接入网设备接收所述终端通过NAS信令消息发送的所述业务数据；所述接入网设备将所述业务数据以及所述第一信息发送给网关，所述网关在接收到所述业务数据以及所述第一信息后，根据所述第一信息对所述业务数据进行计费。

Description

一种业务数据传输方法及设备 技术领域
本发明涉及通信技术领域，尤其涉及一种业务数据传输方法及设备。
背景技术
物联网(英文：Internet of things，简称：IoT)是指把传感器装备各种真实物体，通过互联网联接起来，进而运行特定的程序，达到对物的远程控制或者实现物与物的直接通信的技术。
第三代合作伙伴项目(英文：the 3rd Generation Partnership Project，简称：3GPP)正在开展窄带物联网(英文：Narrow Band Internet of Things，简称：NB-IoT)项目研究，通过整体架构的增强，来支持超低复杂度、功率受限、低数据速率的物联网设备。
NB-IoT终端，比如水表、电表、传感器等，主要发送数据量很小的抄表数据或监测数据，例如，一般只有几十到几百个字节，而且发送间隔时间较大。因此，为了避免传输资源的浪费，将NB-IoT终端的小数据包封装在非接入层(英文：Non-AccessStratum，简称：NAS)信令消息中传输。
但是，采用上述NAS信令消息传输NB-IoT终端数据的方式，网络侧无法获知NB-IoT终端的业务数据信息，导致网络侧无法为不同类型的NB-IoT业务提供针对性服务。
发明内容
本发明提供一种业务数据传输方法及设备，用以解决现有技术中存在的网络侧无法为不同类型的NB-IoT业务提供针对性服务的问题。
第一方面，本发明实施例提供了一种业务数据传输方法，包括：
接入网设备确定终端待发送的业务数据的第一信息，所述第一信息包括业务类型和优先级中的至少一种；然后所述接入网设备接收所述终端通过 NAS信令消息发送的所述业务数据；所述接入网设备将所述业务数据以及所述第一信息通过移动管理实体发送给网关，所述网关在接收到所述业务数据以及所述第一信息后，根据所述第一信息对所述业务数据进行计费。通过在终端通过NAS信令消息发送业务数据之前，接入网确定终端待发送的业务数据的第一信息，然后接入网设备将确定的第一信息发送给网关，使得网关对终端的业务数据提供计费服务，从而解决了现有技术在通过NAS信令消息传输业务数据导致的网络侧无法为不同类型的NB-IoT业务提供针对性服务的问题。
在一种可能的设计中，在所述接入网设备确定终端待发送的业务数据的第一信息之后，所述接入网设备接收所述终端通过非接入层NAS信令消息发送的所述业务数据之前，所述接入网设备根据所述第一信息，对所述业务数据进行传输资源管理。具体的，所述接入网设备根据所述第一信息为所述终端传输所述业务数据分配传输资源，从而使得所述终端通过接入网设备分配的传输资源将业务数据发送给接入网设备。
在一种可能的设计中，所述接入网设备确定终端待发送的业务数据的第一信息，可以通过如下方式实现：
第一种实现方式：
所述接入网设备接收所述终端发送的所述第一信息。
第二种实现方式：
所述接入网设备接收所述终端发送的第二信息，所述第二信息包括所述终端请求传输所述业务数据所采用的业务类型和/或优先级；所述接入网设备将所述第二信息发送给移动管理实体；所述接入网设备接收所述移动管理实体发送的第一业务授权信息，所述第一业务授权信息用于指示允许所述终端传输所述业务数据所采用的业务类型和/或优先级；所述接入网设备根据所述第一业务授权信息，确定所述第一信息。
在一种可能的设计中，所述第一业务授权信息可以包括指示信息，所述指示信息用于指示允许所述第二信息。
第二方面，本发明实施例提供了一种业务数据传输方法，包括：
移动管理实体接收非接入层NAS信令消息，所述NAS信令消息携带终端的业务数据；所述移动管理实体获取所述业务数据的第一信息，所述第一信息包括所述业务数据的业务类型和所述业务数据的优先级中的至少一种；所述移动管理实体将所述业务数据以及所述第一信息发送给网关，所述网关在接收到所述业务数据以及第一信息后，基于所述第一信息对所述业务数据进行计费。通过移动管理实体在NAS信令消息中接收到业务数据后，移动管理实体获取业务数据的第一信息，并在获取后发送给网关，使得网关对终端的业务数据提供计费服务，从而解决了现有技术在通过NAS信令消息传输业务数据导致的网络侧无法为不同类型的NB-IoT业务提供针对性服务的问题。
在一种可能的设计中，所述移动管理实体获取所述业务数据的第一信息，可以通过如下方式实现：
第一种可能的实现方式：
所述移动管理实体接收接入网设备发送的所述第一信息。
第二种可能的实现方式：
所述移动管理实体接收所述终端通过非接入层NAS信令消息发送的所述第一信息。
在一种可能的设计中，所述移动管理实体在接收所述接入网设备发送的所述第一信息之前，所述移动管理实体接收所述接入网设备发送的第二信息，所述第二信息包括所述终端请求传输所述业务数据所采用的业务类型和/或优先级；所述移动管理实体根据所述终端的签约信息，对所述第二信息进行授权得到第一业务授权信息，所述第一业务授权信息用于指示允许所述终端传输所述业务数据所采用的业务类型和/或优先级；所述移动管理实体将所述第一业务授权信息发送给所述接入网设备，以使得所述接入网设备基于所述第一业务授权信息确定所述第一信息。
在一种可能的设计中，所述移动管理实体获取所述业务数据的第一信息，可以通过如下方式实现：
所述移动管理实体接收所述终端发送的所述第一信息。
第三方面，本发明实施例提供了一种业务数据传输方法，包括：
网关接收移动管理实体发送的终端的业务数据和所述业务数据的第一信息，所述第一信息包括业务类型和优先级中的至少一种；
所述网关根据所述第一信息，对所述业务数据进行计费。
第四方面，本发明实施例提供了一种业务数据传输方法，包括：
接入网设备接收移动管理实体通过非接入层NAS信令消息发送的业务数据；所述接入网设备接收所述移动管理实体发送的所述业务数据的信息，所述业务数据的信息包括所述业务数据的业务类型和所述业务数据的优先级中的至少一种；所述接入网设备根据所述业务数据的信息，对所述业务数据进行传输资源管理。针对下行业务数据，移动管理实体会将业务数据以及业务数据的信息发送给接入网设备，接入网设备基于业务数据的信息对自身向终端传输业务数据分配传输资源，从而解决了现有技术在通过NAS信令消息传输业务数据导致的网络侧无法为不同类型的NB-IoT业务提供针对性服务的问题。
第五方面，本发明实施例还提供了一种业务数据传输方法，包括：
移动管理实体接收网关发送的终端的业务数据；所述移动管理实体获取所述业务数据的第一信息，所述第一信息包括业务类型和优先级中的至少一种；所述移动管理实体向接入网设备发送非接入层NAS信令消息，所述NAS信令消息携带所述业务数据；所述移动管理实体将所述第一信息发送给所述接入网设备，所述接入网设备在接收到第一信息后，根据所述第一信息对所述业务数据进行传输资源管理。移动管理实体在接收到终端的业务数据后，会去获取业务数据的第一信息，然后将业务数据以及业务数据的第一信息发送给接入网设备，从而接入网设备根据第一信息对业务数据进行传输资源管理，从而解决了现有技术在通过NAS信令消息传输业务数据导致的网络侧无法为不同类型的NB-IoT业务提供针对性服务的问题。
在一种可能的实现方式中，所述移动管理实体获取所述业务数据的第一 信息，可以通过如下方式实现：
第一种实现方式：
所述移动管理实体根据所述终端的签约信息，确定所述第一信息。
第二种实现方式：
所述业务数据的数据包的包头中携带所述第一信息，所述移动管理实体从所述业务数据的数据包的包头中获取所述第一信息。
第六方面，本发明实施例提供了一种业务数据传输方法，包括：
移动管理实体接收请求消息，所述请求消息包含传输方式指示信息，所述传输方式指示信息用于指示终端采用非接入层NAS信令消息传输业务数据；若所述移动管理实体根据所述请求消息确定所述终端通过非接入层NAS信令消息传输所述业务数据，则所述移动管理实体根据所述终端的签约信息，确定所述终端的第二业务授权信息，所述第二业务授权信息包括用于指示允许所述终端传输业务数据所采用的业务类型和/或优先级的信息；所述移动管理实体将所述第二业务授权信息发送给所述终端。
通过本发明提供的方案，移动管理实体在确定终端采用NAS信令消息传输业务数据时，将终端的第二业务授权信息发送给终端，从而终端基于该第二业务授权信息确定发送的业务数据的信息，并将所述业务数据的信息通知到接入网设备，从而接入网设备基于业务数据的信息对传输业务数据提供服务，从而解决了现有技术在通过NAS信令消息传输业务数据导致的网络侧无法为不同类型的NB-IoT业务提供针对性服务的问题。
在一种可能的设计中，所述第二业务授权信息还包括第一配额信息，所述第一配额信息用于指示在特定时间内允许发送所述业务类型的业务数据的数量。
在一种可能的设计张，所述业务授权信息还包括第二配额信息，所述第二配额信息用于指示在特定时间内允许发送的所述优先级的业务数据的数量。
第七方面，本发明实施例提供了一种业务数据传输方法，包括：
终端发送请求消息给移动管理实体，所述请求消息包含传输方式指示信息，所述传输方式指示信息用于指示终端采用非接入层NAS信令消息传输业务数据；所述终端接收所述移动管理实体发送的第二业务授权信息，所述第二业务授权信息包括用于指示允许所述终端传输业务数据所采用的业务类型和/或优先级的信息；所述终端根据所述第二业务授权信息，确定所述业务数据的信息，所述业务数据的信息包括所述业务数据的业务类型和所述业务数据的优先级中的至少一种；所述终端将所述业务数据的信息发送给所述接入网设备。
通过本发明提供的方案，移动管理实体在确定终端采用NAS信令消息传输业务数据时，将终端的第二业务授权信息发送给终端，从而终端基于该第二业务授权信息确定发送的业务数据的信息，并将所述业务数据的信息通知到接入网设备，从而接入网设备基于业务数据的信息对传输业务数据提供服务，从而解决了现有技术在通过NAS信令消息传输业务数据导致的网络侧无法为不同类型的NB-IoT业务提供针对性服务的问题。
在一种可能的设计中，所述第二业务授权信息还包括第一配额信息，所述第一配额信息用于指示在特定时间内被允许发送所述业务类型的业务数据的数量。
在一种可能的设计中，所述第二业务授权信息还包括第二配额信息，所述配额信息用于指示在特定时间内允许发送所述优先级的业务数据的数量。
第八方面，本发明实施例提供了一种接入网设备，包括：
处理器，用于确定终端待发送的业务数据的第一信息，所述第一信息包括业务类型和优先级中的至少一种；
接收器，用于接收所述终端通过非接入层NAS信令消息发送的所述业务数据；
通信接口，用于将所述接收器接收到的所述业务数据以及所述处理器确定的所述第一信息通过移动管理实体发送给网关，以使得所述网关根据所述第一信息对所述业务数据进行计费。
在一种可能的设计中，在所述处理器确定终端待发送的业务数据的第一信息之后，所述接收器接收所述终端通过非接入层NAS信令消息发送的所述业务数据之前，所述处理器，还用于根据所述第一信息，对所述业务数据进行传输资源管理。
在一种可能的设计中，所述接收器，还用于接收所述终端发送的所述第一信息。
在一种可能的设计中，所述接收器，还用于接收所述终端发送的第二信息，所述第二信息包括所述终端请求传输所述业务数据所采用的业务类型和/或优先级；
所述通信接口，还用于将所述第二信息发送给移动管理实体；
所述通信接口，还用于接收所述移动管理实体发送的第一业务授权信息，所述第一业务授权信息用于指示允许所述终端传输所述业务数据所采用的业务类型和/或优先级；
所述处理器，具体用于根据所述第一业务授权信息，确定所述第一信息。
在一种可能的设计中，所述第一业务授权信息包括指示信息，所述指示信息用于指示允许所述第二信息。
第九方面，本发明实施例提供了一种移动管理实体，包括：
通信接口，用于接收非接入层NAS信令消息，所述NAS信令消息携带终端的业务数据；
处理器，用于获取所述通信接口接收到的所述业务数据的第一信息，所述第一信息包括所述业务数据的业务类型和所述业务数据的优先级中的至少一种；
所述通信接口，还用于将所述业务数据以及所述第一信息发送给网关，以使得所述网关对所述业务数据进行计费。
在一种可能的设计中，所述通信接口，还用于接收接入网设备发送的所述第一信息；或者，
所述通信接口，还用于接收所述终端通过非接入层NAS信令消息发送的 所述第一信息。
在一种可能的设计中，所述通信接口，在接收所述接入网设备发送的所述第一信息之前，还用于接收所述接入网设备发送的第二信息，所述第二信息包括所述终端请求传输所述业务数据所采用的业务类型和/或优先级；
所述处理器，还用于根据所述终端的签约信息，对所述第二信息进行授权得到第一业务授权信息，所述第一业务授权信息用于指示允许所述终端传输所述业务数据所采用的业务类型和/或优先级；
所述通信接口，还用于将所述第一业务授权信息发送给所述接入网设备，以使得所述接入网设备基于所述第一业务授权信息确定所述第一信息。
在一种可能的设计中，所述接收器，还用于接收所述终端发送的所述第一信息。
第十方面，本发明实施例提供了一种网关，包括：
通信接口，用于接收移动管理实体发送的终端的业务数据和所述业务数据的第一信息，所述第一信息包括业务类型和优先级中的至少一种；
处理器，用于根据所述通信接口接收到的所述第一信息，对所述业务数据进行计费。
第十一方面，本发明实施例提供了一种接入网设备，包括：
通信接口，用于接收移动管理实体通过非接入层NAS信令消息发送的业务数据；以及接收所述移动管理实体发送的所述业务数据的信息，所述业务数据的信息包括业务类型和优先级中的至少一种；
处理器，用于根据所述业务数据的信息，对所述业务数据进行传输资源管理。
第十二方面，本发明实施例提供了一种移动管理实体，包括：
通信接口，用于接收网关发送的终端的业务数据；
处理器，用于获取所述通信接口接收到的所述业务数据的第一信息，所述第一信息包括业务类型和优先级中的至少一种；
所述通信接口，用于向接入网设备发送非接入层NAS信令消息，所述 NAS信令消息携带所述业务数据；并将所述第一信息发送给所述接入网设备，以使得所述接入网设备根据所述第一信息对所述业务数据进行传输资源管理。
在一种可能的设计中，所述处理器具体用于根据所述终端的签约信息，确定所述第一信息；或者，
所述业务数据的数据包的包头中携带所述第一信息，所述处理器具体用于从所述业务数据的数据包的包头中获取所述第一信息。
第十三方面，本发明实施例提供了一种移动管理实体，包括：
通信接口，用于接收请求消息，所述请求消息包含传输方式指示信息，所述传输方式指示信息用于指示终端采用非接入层NAS信令消息传输业务数据；
处理器，用于在根据所述请求消息确定所述终端通过非接入层NAS信令消息传输所述业务数据时，则根据所述终端的签约信息，确定所述终端的第二业务授权信息，所述第二业务授权信息包括用于指示允许所述终端传输业务数据所采用的业务类型和/或优先级的信息；
所述通信接口，还用于将所述第二业务授权信息发送给所述终端。
在一种可能的设计中，所述第二业务授权信息还包括第一配额信息，所述第一配额信息用于指示在特定时间内允许发送所述业务类型的业务数据的数量。
在一种可能的设计中，所述业务授权信息还包括第二配额信息，所述第二配额信息用于指示在特定时间内允许发送的所述优先级的业务数据的数量。
第十四方面，本发明实施例提供了一种终端，包括：
发射器，用于发送请求消息给移动管理实体，所述请求消息包含传输方式指示信息，所述传输方式指示信息用于指示终端采用非接入层NAS信令消息传输业务数据；
接收器，用于接收所述移动管理实体发送的第二业务授权信息，所述第 二业务授权信息包括用于指示允许所述终端传输业务数据所采用的业务类型和/或优先级的信息；
处理器，用于根据所述第二业务授权信息，确定所述业务数据的信息，所述业务数据的信息包括所述业务数据的业务类型和所述业务数据的优先级中的至少一种；
所述发射器，还用于将所述处理器确定的所述业务数据的信息发送给所述接入网设备。
在一种可能的设计中，所述第二业务授权信息还包括第一配额信息，所述第一配额信息用于指示在特定时间内被允许发送所述业务类型的业务数据的数量。
在一种可能的设计中，所述第二业务授权信息还包括第二配额信息，所述配额信息用于指示在特定时间内允许发送所述优先级的业务数据的数量。
第十五方面，本发明实施例提供了一种接入网设备，包括：
确定单元，用于确定终端待发送业务数据的第一信息，所述第一信息包括业务类型和优先级中的至少一种；
接收单元，用于接收所述终端通过非接入层NAS信令消息发送的所述业务数据；
发送单元，用于将所述接收单元接收到的所述业务数据以及所述确定单元确定的所述第一信息通过移动管理实体发送给网关，以使得所述网关根据所述第一信息对所述业务数据进行计费。
在一种可能的设计中，还包括：管理单元，用于在所述确定单元确定终端待发送的业务数据的第一信息之后，所述接收单元接收所述终端通过非接入层NAS信令消息发送的所述业务数据之前，根据所述第一信息对所述业务数据进行传输资源管理。
在一种可能的设计中，所述确定单元，具体用于在所述接收单元接收到所述终端发送的所述第一信息，则确定所述第一信息。
在一种可能的设计中，所述接收单元，还用于接收所述终端发送的第二 信息，所述第二信息包括所述终端请求传输所述业务数据所采用的业务类型和/或优先级；
所述发送单元，还用于将所述第二信息发送给移动管理实体；
所述接收单元，还用于接收所述移动管理实体发送的第一业务授权信息，所述第一业务授权信息用于指示允许所述终端传输所述业务数据所采用的业务类型和/或优先级；
所述确定单元，具体用于根据所述第一业务授权信息，确定所述第一信息。
在一种可能的设计中，所述第一业务授权信息包括指示信息，所述指示信息用于指示允许所述第二信息。
第十六方面，本发明实施例提供了移动管理实体，包括：
接收单元，用于接收非接入层NAS信令消息，所述NAS信令消息携带终端的业务数据；
获取单元，用于获取所述接收单元接收到的所述业务数据的第一信息，所述第一信息包括所述业务数据的业务类型和所述业务数据的优先级中的至少一种；
发送单元，用于将所述业务数据以及所述第一信息发送给网关，以使得所述网关对所述业务数据进行计费。
在一种可能的设计中，所述获取单元，具体用于在所述接收单元接收到接入网设备发送的所述第一信息，则获取到所述第一信息；或者
所述获取单元，具体用于在所述接收单元接收到所述终端通过NAS信令消息发送的所述第一信息，则获取到所述第一信息。
在一种可能的设计中，所述接收单元在接收所述接入网设备发送的所述第一信息之前，还用于接收所述接入网设备发送的第二信息，所述第二信息包括所述终端请求传输所述业务数据所采用的业务类型和/或优先级；
所述移动管理实体还包括授权单元，用于根据所述终端的签约信息，对所述第二信息进行授权得到第一业务授权信息，所述第一业务授权信息用于 指示允许所述终端传输所述业务数据所采用的业务类型和/或优先级；
所述发送单元，还用于将所述第一业务授权信息发送给所述接入网设备，以使得所述接入网设备基于所述第一业务授权信息确定所述第一信息。
在一种可能的设计中，所述获取单元，具体用于在所述接收单元接收到所述终端发送的所述第一信息时，则获取到所述第一信息。
第十七方面，本发明实施例提供了一种网关，包括：
接收单元，用于接收移动管理实体发送的终端的业务数据和所述业务数据的第一信息，所述第一信息包括业务类型和优先级中的至少一种；
计费单元，用于根据所述第一信息，对所述业务数据进行计费。
第十八方面，本发明实施例还提供了一种接入网设备，包括：
接收单元，用于接收移动管理实体通过非接入层NAS信令消息发送的业务数据；以及接收所述移动管理实体发送的所述业务数据的信息，所述业务数据的信息包括所述业务数据的业务类型和所述业务数据的优先级中的至少一种；
管理单元，用于根据所述接收单元接收到的所述业务数据的信息，对所述业务数据进行传输资源管理。
第十九方面，本发明实施例提供了一种移动管理实体，包括：
接收单元，用于接收网关发送的终端的业务数据；
获取单元，用于获取所述接收单元接收到的所述业务数据的第一信息，所述第一信息包括所述业务数据的业务类型和所述业务数据的优先级中的至少一种；
发送单元，用于向接入网设备发送非接入层NAS信令消息，所述NAS信令消息携带所述获取单元获取到的所述业务数据；将所述第一信息发送给所述接入网设备，以使得所述接入网设备根据所述第一信息对所述业务数据进行传输资源管理。
在一种可能的设计中，所述获取单元，具体用于根据所述终端的签约信息，确定所述第一信息；或者，
所述业务数据的数据包的包头中携带所述第一信息，所述获取单元备从所述业务数据的数据包的包头中获取所述第一信息。
第二十方面，本发明实施例提供了一种移动管理实体，包括：
接收单元，用于接收请求消息，所述请求消息包含传输方式指示信息，所述传输方式指示信息用于指示终端采用非接入层NAS信令消息传输业务数据；
确定单元，用于在根据所述请求消息确定所述终端通过非接入层NAS信令消息传输所述业务数据，则根据所述终端的签约信息，确定所述终端的第二业务授权信息，所述第二业务授权信息包括用于指示允许所述终端传输业务数据所采用的业务类型和/或优先级的信息；
发送单元，用于将所述确定单元确定的所述第二业务授权信息发送给所述终端。
在一种可能的设计中，所述第二业务授权信息还包括第一配额信息，所述第一配额信息用于指示在特定时间内允许发送所述业务类型的业务数据的数量。
在一种可能的设计中，所述业务授权信息还包括第二配额信息，所述第二配额信息用于指示在特定时间内允许发送的所述优先级的业务数据的数量。
第二十一方面，本发明实施例提供了一种终端，包括：
发送单元，用于发送请求消息给移动管理实体，所述请求消息包含传输方式指示信息，所述传输方式指示信息用于指示终端采用非接入层NAS信令消息传输业务数据；
接收单元，用于接收所述移动管理实体发送的第二业务授权信息，所述第二业务授权信息包括用于指示允许所述终端传输业务数据所采用的业务类型和/或优先级的信息；
确定单元，用于根据所述接收单元接收到的所述第二业务授权信息，确定所述业务数据的信息，所述业务数据的信息包括所述业务数据的业务类型 和所述业务数据的优先级中的至少一种；
所述发送单元，还用于将所述确定单元确定的所述业务数据的信息发送给所述接入网设备。
在一种可能的设计中，所述第二业务授权信息还包括第一配额信息，所述第一配额信息用于指示在特定时间内被允许发送所述业务类型的业务数据的数量。
在一种可能的设计中，所述第二业务授权信息还包括第二配额信息，所述配额信息用于指示在特定时间内允许发送所述优先级的业务数据的数量。
附图说明
图1为本发明实施例提供的EPS网络系统架构图；
图2为本发明实施例一提供的一种业务数据传输方法流程图；
图3为本发明实施例一提供的另一种业务数据传输方法流程图；
图4为本发明实施例一提供的又一种业务数据传输方法流程图；
图5为本发明实施例一提供的再一种业务数据传输方法流程图；
图6为本发明实施例一提供的一种业务数据传输方法示意图；
图7为本发明实施例一提供的另一种业务数据传输方法示意图；
图8为本发明实施例一提供的再一种业务数据传输方法流程图；
图9为本发明实施例一提供的又一种业务数据传输方法示意图；
图10为本发明实施例二提供的一种业务数据传输方法流程图；
图11为本发明实施例二提供的一种业务数据传输方法示意图；
图12为本发明实施例三提供的一种业务数据传输方法流程图；
图13为本发明实施例三提供的一种业务数据传输方法示意图；
图14为本发明实施例提供的一种接入网设备示意图；
图15为本发明实施例提供的另一种接入网设备示意图；
图16为本发明实施例提供的一种移动管理实体示意图；
图17为本发明实施例提供的另一种移动管理实体示意图；
图18为本发明实施例提供的一种网关示意图；
图19为本发明实施例提供的另一种网关示意图；
图20为本发明实施例提供的又一种接入网设备示意图；
图21为本发明实施例提供的再一种接入网设备示意图；
图22为本发明实施例提供的又一种移动管理实体示意图；
图23为本发明实施例提供的再一种移动管理实体示意图；
图24为本发明实施例提供的再一种移动管理实体示意图；
图25为本发明实施例提供的再一种移动管理实体示意图；
图26为本发明实施例提供的一种终端示意图；
图27为本发明实施例提供的另一种终端示意图。
具体实施方式
为了使本发明的目的、技术方案和优点更加清楚，下面将结合附图对本发明作进一步地详细描述，显然，所描述的实施例仅仅是本发明一部分实施例，而不是全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其它实施例，都属于本发明保护的范围。
本发明提供一种业务数据传输方法及设备，用以解决现有技术中存在的网络侧无法为不同类型的NB-IoT业务提供针对性服务的问题。其中，方法和设备是基于同一发明构思的，由于方法及设备解决问题的原理相似，因此设备与方法的实施可以相互参见，重复之处不再赘述。本发明实施例中使用的“和/或”，既可以是“和“的关系，还可以是“或”的关系，例如A和/或B，既可以单独为A、或者单独为B，还可以是A和B。
应理解，在本发明实施例中，终端(Terminal)可以称之为用户设备(英文：User Equipment，简称：UE)、移动台(英文：Mobile Station，简称：MS)或移动终端(Mobile Terminal)等，该终端可以经无线接入网(英文：Radio Access Network，简称：RAN)与一个或多个核心网设备进行通信，例如，终 端可以是移动电话(或称为“蜂窝”电话)或具有移动终端的计算机等，例如，终端还可以是便携式、袖珍式、手持式、计算机内置的或者车载的移动设备，它们与无线接入网交换语音和/或数据。
还应理解，本发明实施例中提供的技术方案，可以应用于各种通信系统，例如：全球移动通信系统(英文：Global System of Mobile communication，简称：GSM，)，码分多址(英文：Code Division Multiple Access，简称：CDMA)系统，宽带码分多址(英文：Wideband Code Division Multiple Access Wireless，简称：WCDMA)系统，通用分组无线业务(英文：General Packet Radio Service，简称：GPRS)系统，长期演进(英文：Long Term Evolution，简称：LTE)系统、演进分组系统(英文：Evolved Packet System，简称：EPS)等。
本发明实施例中以应用到EPS系统为例来说明。如图1所示为EPS网络系统架构图。EPS网络系统包括：UE，演进的通用陆基无线接入网(英文：Evolved universal terrestrial radio access network，简称：EUTRAN)，移动性管理实体(英文：Mobility Management Entity，简称：MME)，服务网关(英文：Serving Gateway，简称：S-GW)，分组数据网络网关(英文：Packet Data Network Gateway，简称：P-GW)，服务GPRS支持节点(英文：Serving GPRS Support Node，简称：SGSN)，归属签约用户服务器(英文：Home Subscriber Server，简称：HSS)，策略与计费规则功能单元(英文：Policy and Charging Rules Function，简称：PCRF)以及运营商互联网协议(英文：Internet Protocol，简称：IP)服务(Operator's IP Services)。
EUTRAN：由多个演进型节点(英文：Evolved Node B，简称：eNB)组成的网络，能够实现无线物理层功能、资源调度和无线资源管理、无线接入控制以及移动性管理功能。eNB通过用户面接口S1-U与服务网关(英文：Serving Gateway，简称：S-GW)相连，用于传送用户数据；通过控制面接口S1-MME与MME相连，采用S1-AP协议实现无线接入承载控制等功能。
MME：主要负责用户即会话管理的所有控制平面功能，包括NAS信令及安全，跟踪区的管理，P-GW与S-GW的选择等。
S-GW：主要负责UE的数据传输、转发以及路由切换等，并作为UE在eNB之间切换时的本地移动性锚定点。其中，对于每一个UE，每个时刻仅有一个S-GW为之服务。
P-GW：作为分组数据网络(英文：Packet Data Network Gateway，简称：PDN)连接的锚定点，负责UE的IP地址分配，UE的数据报文过滤、速率控制、生成计费信息等。
HSS：是用于存储用户签约信息的数据库，该设备的主要功能是存储用户签约信息、用户鉴权、以及位置信息管理等。
PCRF：用于基于业务数据流的QoS控制、门控以及计费控制等。
SGSN：主要完成分组数据包的路由转发、移动性管理、会话管理、逻辑链路管理、鉴权和加密、话单产生和输出等功能。
NB-IoT中的业务数据的业务类型，如表1所示。
表1
Figure PCTCN2016092521-appb-000001
Figure PCTCN2016092521-appb-000002
针对NB-IoT业务的服务质量需求分析如下：
上行部分：
1)、例外报告的优先级高于周期性报告的优先级，要求优先调度和传输例外报告，做到准实时，时延小于10s，而周期性报告对时延不敏感，可以延迟发送。
2)、某些终端会发送周期性报告或者例外报告，网络侧无法根据终端确定其数据报告的类型，只有终端知道其发送的数据报告类型，因此网络侧无法为其提供服务，因此本发明中由终端通知网络侧。
3)、某些终端发送例外报告的频度较低(如智能水表、智能电表等)、某些终端发送例外报告的频度较高(如智能停车、水泵控制)，本发明实施例提供的方案能控制例外报告的使用。
下行部分：
4)、下行需要区分业务优先级，优先调度和传输高优先级的控制命令。
5)、部分用户可能同时存在高优先级的控制命令和低优先级的参数配置、软件升级等业务，部分用户只有低优先级的参数配置、软件升级等业务，因此需要区分不同用户发送的不同的业务数据的优先级。
6)、因为参数配置、软件升级的频度非常低，本发明实施例中可以实施按用户类型来区分业务优先级，高优先级用户的业务为高优先级业务，低优先级用户的业务为低优先级业务。
本发明实施例中所涉及的第一信息包括终端业务数据的优先级和业务数据的业务类型中的至少一种；第二信息包括所述终端请求传输所述业务数据所采用的业务类型和/或优先级。
实施例一
基于针对上述NB-IoT业务的服务质量需求分析，本发明实施例提出了业务数据传输方法，移动管理实体通过NAS信令消息接收终端的业务数据，并 获取所述业务的第一信息，然后将所述业务数据以及所述第一信息发送给网关，从而网关能够基于该第一信息对该业务数据提供计费服务，从而控制终端的高优先级报告的使用。如图2所示，该方法包括：
S201，移动管理实体接收NAS信令消息，NAS信令消息携带终端的业务数据。
S202，移动管理实体获取所述业务数据的第一信息，所述第一信息包括业务类型和优先级中的至少一种。
需要说明的是，业务类型可以是周期性报告也可以是例外报告，优先级可以为第一优先级也可以为第二优先级，其中第一优先级高于第二优先级。
S203，所述移动管理实体将所述业务数据以及所述第一信息发送给网关。
S204，所述网关在接收所述业务数据以及所述第一信息后，基于所述第一信息对所述业务数据进行计费。
需要指出的是，上述接入网设备可以为eNB，移动管理实体可以为MME，网关可以为S-GW或P-GW，此处不予限制。
需要说明的是，本发明各实施例中的网关，接入网设备以及移动管理实体可以是独立的物理设备，也可是软件功能实体，或者具体同等功能的设备，不予限制。
移动管理实体通过NAS信令消息接收终端的业务数据，并获取所述业务的第一信息，然后将所述业务数据以及所述第一信息发送给网关，从而网关能够基于该第一信息对该业务数据提供计费服务。通过针对不同的业务类型或者优先级的业务数据进行计费控制，从而能够控制终端在发送业务数据时，依据需求对业务数据的第一信息进行配置，避免了低优先级终端，比如以周期性报告为主的终端(智能水表)，过度使用高优先级报告(例外报告)。从而减少由于多数终端均采用高优先级或者例外报告发送业务数据造成的数据传输拥塞。
本发明实施例中，可以配置针对业务数据的流量进行计费，或者根据业务数据的数据包个数进行计费，或者根据发送高优先级或者业务类型为例外 报告的业务数据的次数进行计费。具体的，可以根据优先级设置不同的计费标准，高优先级的业务数据收费高于低优先级的业务数据。例如：同样发送10M流量的业务数据，若以高优先级发送，则计费人民币1元，若以低优先级发送计费人民币0.1元。还可以根据业务类型设置不同的计费标准，业务类型为例外报告的业务数据的计费高于业务类型为周期性报告的业务数据的计费。比如，同样发送一次业务数据，若通过周期报告发送，则计费0.1元，若通过例外报告发送，则计费0.5元。
其中，在S201中移动管理实体接收到NAS信令消息，具体可以是由接入网设备发送的，也可以是由终端发送的。
在步骤S202中移动管理实体获取所述第一信息，可以是由接入网设备发送的，也可以是由终端发送的。
因此，在上述实施例一的第一种应用场景下，移动管理实体接收接入网设备发送的NAS信令消息以及业务数据的第一信息。在上述实施例一的第二种应用场景下，移动管理实体接收终端发送的NAS信令消息以及业务数据的第一信息。
下面针对上述实施例一的第一种实施场景进行说明，即移动管理实体接收接入网设备发送的NAS信令消息以及业务数据的第一信息，其中NAS信息消息中携带有终端的业务数据。参见图3所示。
S301，接入网设备确定终端待发送的业务数据的第一信息，所述第一信息包括业务类型和优先级中的至少一种。
S302，所述接入网设备接收所述终端通过NAS信令消息发送的所述业务数据；
S303，所述接入网设备将所述业务数据以及所述第一信息发送给移动管理实体；
S304，所述移动管理实体将所述业务数据以及所述第一信息发送给网关；
S305，所述网关根据所述第一信息对所述业务数据进行计费。
可选地，在步骤S301之后以及步骤S302之前，即接入网设备在接收终 端发送的第一信息后，上述方法还包括：
S301a，所述接入网设备根据所述第一信息，对所述业务数据进行传输资源管理。
具体的，基于该第一信息对所述业务数据进行传输资源管理可以是基于第一信息为待发送的业务数据分配传输资源，即网络资源。比如，终端待传输的业务数据的业务类型为例外报告，例外报告对传输时延有要求，因此接入网设备为该业务数据分配的网络资源要满足例外报告的时延要求。进而终端在步骤S301a中分配的网络资源向接入网设备发送携带有该业务数据的NAS信令。
可选地，上述步骤S301具体可以包括：S3010a(如图4所示)或者S3010b-S3010g(如图5所示)。
S3010a，接入网设备接收所述终端发送的所述第一信息。
可选地，接入网设备接收终端发送的无线资源控制(英文：Radio Resource Control，简称：RRC)连接建立请求消息，该连接建立请求消息中携带所述第一信息。
S3010b，所述接入网设备接收所述终端发送的第二信息。
其中，所述第二信息可以包括所述终端请求传输所述业务数据所采用的业务类型和/或优先级。
可选地，接入网设备接收终端发送的RRC连接建立请求消息，该连接建立请求消息中携带所述第二信息。
S3010c，所述接入网设备将所述第二信息发送给移动管理实体。
S3010d，所述移动管理实体接收所述接入网设备发送的所述第二信息，并对所述第二信息进行授权得到第一业务授权信息。
具体的，所述移动管理实体对接收到的所述接入网设备发送的所述第二信息进行授权时，根据所述终端的签约信息对所述第二信息进行得到第一业务授权信息。
其中，第一业务授权信息可以是包括指示信息，所述指示信息用于指示 允许所述第二信息，或者拒绝所述第二信息。
S3010e，所述移动管理实体将所述第一业务授权信息发送给所述接入网设备。
S3010f，所述接入网设备接收所述移动管理实体发送的第一业务授权信息，所述第一业务授权信息用于指示允许所述终端传输所述业务数据所采用的业务类型和/或优先级。
S3010g，所述接入网设备根据所述第一业务授权信息，确定所述第一信息。
其中，所述第一业务授权信息可以包括指示信息，所述指示信息用于指示允许所述第二信息。
其中，所述第一信息包括所述终端待发送的业务数据的业务类型和所述业务数据的优先级中的至少一种。
具体的，若第一业务授权信息是允许所述第二信息，则接入网设备确定的第一信息与第二信息相同，若第一业务授权信息是拒绝所述第二信息，则接入网设备确定的第一信息与第二信息不同。例如第二信息包括的业务类型为例外报告，若第一业务授权信息为允许终端发送例外报告，则接入网设备确定的第二信息包括的业务类型为例外报告，若第一业务授权信息为拒绝终端发送例外报告，则接入网设备确定的第二信息包括的业务类型为周期性报告。
具体的，移动管理实体对所述第二信息进行授权得到第一业务授权信息时，移动管理实体根据所述终端的签约信息对所述第二信息进行授权得到第一业务授权信息。
在一种可能的实现方式中，签约信息中可以包括允许终端发送的业务数据的优先级或者业务数据的业务类型。例如：签约信息中包括允许终端发送的业务数据的业务类型为周期性报告，若第二信息为例外报告，则移动管理实体根据签约信息对所述第二信息进行授权得到第一业务授权信息为拒绝第二信息。
在本发明实施例中通过为每个终端配置可发送的业务数据的优先级或者业务数据的业务类型，从而能够避免低优先级终端(以周期性报告为主的终端，如智能水表)使用高优先级报告，从而避免多数终端均采用高优先级的发送业务数据造成的数据传输拥塞。
在另一种可能的实现方式中，签约信息中可以包括允许终端发送的业务数据的优先级以及优先级对应的配额信息，所述优先级对应的配额信息用于指示在特定时间内允许发送所述优先级的业务数据的数量。这里优先级为高优先级。数量可以是业务数据的流量或者发送业务数据的次数等。
在本发明实施例中通过为每个终端配置可发送的业务数据的优先级以及优先级对应的配额信息，从而对终端发送的高优先级的业务数据超过配额信息时，则拒绝请求，则接入网设备按照低优先级发送所述业务数据，从而能够避免低优先级终端(以周期性报告为主的终端，如智能水表)过度使用高优先级报告，从而避免多数终端均采用高优先级的发送业务数据造成的数据传输拥塞。
在又一种可能的实现方式中，签约信息中可以包括允许终端发送的业务数据的业务数据的业务类型和业务类型对应的配额信息，所述业务类型对应的配额信息用于指示在特定时间内允许发送所述业务类型的业务数据的数量。
在本发明实施例中通过为每个终端配置可发送的业务数据的业务数据的业务类型以及配额信息，从而对终端发送的业务类型为例外报告的业务数据超过配额信息时，则拒绝请求，则按照周期性报告发送，从而能够避免低优先级终端(以周期性报告为主的终端，如智能水表)过度使用例外报告，从而减少由于多数终端均采用例外报告来发送业务数据造成的数据传输拥塞。
可选地，接入网设备接收到终端发送的第二信息包括的业务数据的业务类型为例外报告或者业务数据的优先级为高优先级时，所述接入网设备将所述业务数据的第二信息发给移动管理实体进行授权。因此，步骤S3010c之前，还包括：S3010cb，所述接入网设备确定接收到终端发送的第二信息包括的业 务数据的业务类型为例外报告或者优先级为高优先级。
若接入网设备确定接收到终端发送的第二信息包括的业务数据的业务类型为周期性报告或者优先级为低优先级，则接入网设备可以不去移动管理实体对第二信息进行授权，而是直接将第二信息发送给网关，以使得移动管理实体对所述业务数据进行计费。
下面以EPS系统为例，对上述图4对应的实施例进行具体说明，如图6所示。以接入网设备为基站、终端称之为UE，移动管理实体为MME、网关包括S-GW以及P-GW为例，说明如下：
S601，UE向基站(英文：Base Station，简称BS)发起RRC连接建立请求消息。
其中RRC建立原因值指示第一信息。第一信息包括该业务数据的优先级和业务数据的业务类型中的至少一种。该实施例中以优先级为例。优先级包括第一优先级和第二优先级，其中第一优先级高于第二优先级。
S602，基站根据UE所指示RRC建立原因值为终端传输业务数据分配传输资源。
S603，UE将业务数据封装在NAS信令消息发送给基站。
具体的，该NAS信令消息可以通过RRC建立连接完成(RRC Connection Setup Complete)消息传输到基站。
终端在发送业务数据时，通过基站分配的传输资源来向基站发送业务数据。
S604，基站接收终端发送的NAS信令消息，并将该NAS信令消息以及该业务数据对应的优先级发送给MME。
其中，基站在向MME发送业务数据以及业务数据的优先级时，可以通过接口S1AP初始UE消息(S1AP Initial UE message)发送。
S605，MME在接收到NAS信令消息以及业务数据的优先级后，从NAS信令消息中获取业务数据，并将业务数据以及业务数据的优先级发送给S-GW。
具体的，MME将业务数据封装到用户层面的GPRS隧道协议(英文：GPRS Tunnel Protocol User Plane，简称：GTP-U)数据包中发送给S-GW，其中，GTP-U数据包的包头中携带该业务数据的优先级。
S606，S-GW根据业务数据的优先级对该业务数据进行计费。S-GW可以生成计费数据S-GW计费数据记录(英文：Charging Data Record，简称：CDR)，并且该CDR中记录该业务数据的优先级。
S607，S-GW将该业务数据以及业务数据的优先级发送给P-GW，。
具体的，S-GW将业务数据封装到GTP-U数据包中发送给S-GW，其中，GTP-U数据包的包头中携带该业务数据的优先级。
S608，P-GW根据业务数据的优先级对业务数据进行计费。
P-GW可以生成计费数据P-GW CDR，并且该CDR中记录该业务数据的优先级。
终端在发送业务数据之前，将业务数据的优先级发送给基站，从而在基站接收到终端发送的业务数据后，通过MME将业务数据以及业务数据的优先级发送给P-GW以及S-GW，从而P-GW以及S-GW基于业务数据的优先级对业务数据进行计费控制，即高优先级的业务数据传输以及低优先级的业务数据传输采用不同计费标准，基站在传输业务数据时将业务数据的优先级发送给P-GW以及S-GW，从而P-GW以及S-GW根据业务数据的优先级对业务数据提供计费服务。另外，还避免了低优先级终端(以周期性报告为主的中终端)过度通过高优先级来传输业务数据，减少了由于多数终端均采用高优先级的发送业务数据造成的数据传输拥塞。
下面以EPS系统为例对上述图5对应的实施例进行具体说明，如图7所示。其中，接入网设备为NB-IoT BS、终端为NB-IoT UE，移动管理实体为MME，网关包括S-GW以及P-GW。
S701，UE向基站发起RRC连接建立请求消息。
其中，该RRC连接建立请求消息中RRC建立原因值指示第二信息。第二信息包括该UE请求传输业务数据所采用的优先级和/或业务类型。该实施 例中以业务类型为例。业务类型可以是例外报告或者周期性报告，其中第一优先级高于第二优先级。
S702，基站在接收到所述RRC连接建立请求消息后，确定UE所指示RRC建立原因值指示的业务类型为例外报告，向MME请求发送例外报告授权。
S703，MME根据签约信息确定对所述业务数据的第二信息的第一业务授权信息，所述第一业务授权信息用于指示允许所述终端传输所述业务数据所采用的业务类型。
其中，在一种可能的实现方式中，签约信息中可以包括允许终端传输业务数据所能采用的业务数据的业务类型。若签约信息中不允许终端发送例外报告，则第一业务授权信息指示接入网设备以周期性报告调度所述业务数据所需的传输资源。若签约信息中允许终端发送例外报告，则业务授权信息指示接入网设备以例外报告调度所述业务数据所需的传输资源。即业务授权信息包括允许第二信息或者拒绝第二信息。
在一种可能的实现方式中，签约信息中可以包括允许终端传输业务数据所采用的例外报告以及例外报告对应的配额信息，所述配额信息用于指示在特定时间内允许发送业务类型为例外报告的业务数据的数量。数量可以是业务数据的流量或者发送业务数据的次数等。MME确定终端需发送的业务类型为例外报告的业务数据的数量超过配额信息时，则拒绝请求，指示接入网设备按照周期性报告调度该业务数据的传输资源。MME确定终端需发送的业务类型为例外报告的业务数据的数量未超过配额信息时，则接受请求，指示接入网设备按照例外报告调度该业务数据的传输资源。MME还可以基于签约信息生成第三业务授权信息发送给接入网设备，第三业务授权信息中包括允许终端例外报告以及例外报告对应的配额信息，从而接入网设备基于第三业务授权信息确定终端能够发送业务类型为例外报告的业务数据时，则按照例外报告为该终端需发送的业务数据分配传输资源。否则按周期性报告为该终端需发送的业务数据分配传输资源。
S704，MME将第一业务授权信息发送给基站。
S705，基站根据所述第一业务授权信息为终端传输所述业务数据分配传输资源。
S706，基站在接收终端通过NAS信令消息发送的业务数据后，将该业务数据转发给MME，并通知MME该业务数据的业务类型为例外报告。
S707，MME在接收到业务数据以及业务数据的业务类型后，将业务数据以及业务数据的业务类型发送给S-GW。
具体的，MME将业务数据封装到用户层面的GPRS隧道协议(英文：GPRS Tunnel Protocol User Plane，简称：GTP-U)数据包中发送给S-GW，其中，GTP-U数据包的包头中携带该业务数据的业务类型。
S708，S-GW根据业务数据的业务类型对该业务数据进行计费。S-GW可以生成计费数据S-GW计费数据记录(英文：Charging Data Decord，简称：CDR)，并且该CDR中记录该业务数据的业务类型。
S709，S-GW将该业务数据以及业务数据的业务类型发送给P-GW。
具体的，S-GW将业务数据封装到GTP-U数据包中发送给S-GW，其中，GTP-U数据包的包头中携带该业务数据的业务类型。
S710，P-GW根据业务数据的业务类型对业务数据进行计费。
P-GW可以生成计费数据P-GW CDR，并且该CDR中记录该业务数据的业务类型。
下面针对上述实施例一的第二种实施场景进行说明，即移动管理实体接收终端发送的NAS信令消息。其中NAS信息消息中携带终端的业务数据以及业务数据的第一信息。参见图8所示。
S801，移动管理实体接收终端通过NAS信令消息发送的业务数据以及业务数据的信息，业务数据的信息包括业务类型和优先级中的至少一种。
S802，所述移动管理实体将所述业务数据以及业务数据的信息发送给网关。
S803，所述网关根据所述业务数据的信息对所述业务数据进行计费。
本发明实施例中终端将业务数据以及业务数据的信息通过NAS信令消息 发给移动管理实体，移动管理实体将业务数据以及业务数据的信息发送给网关，从而网关根据业务数据的信息对业务数据进行计费处理。通过针对不同的业务类型或者优先级的业务数据进行计费控制，能够控制终端在发送业务数据时，依据需求对业务数据的业务类型或者优先级进行配置，避免了低优先级终端，比如以周期性报告为主的终端(智能水表)，过度使用高优先级报告(例外报告)。
下面以EPS系统为例对上述图8对应的第二种实施场景进行具体说明，如图9所示。其中，接入网设备为基站、终端为UE，移动管理实体包括MME，网关包括S-GW以及P-GW。
S901，接入网设备接收终端发送的RRC连接建立完成消息，该消息中携带包括了业务数据以及该业务数据的信息的NAS信令消息。
S902，接入网设备将接收到NAS信令消息转发给MME。
S903，MME从终端发送的NAS信令消息中获取业务数据以及该业务数据的信息；业务数据的信息包括业务数据的业务类型和业务数据的优先级中的至少一种。在该实施例中以业务数据的信息包括业务数据的优先级为例。
S904，MME在获取到业务数据以及业务数据的优先级后，将业务数据以及业务数据的优先级发送给S-GW。
具体的，MME将业务数据封装到GTP-U数据包中发送给S-GW，其中，GTP-U数据包的包头中携带该业务数据的优先级。
S905，S-GW根据业务数据的优先级对该业务数据进行计费。S-GW可以生成计费数据S-GW CDR，并且该CDR中记录该业务数据的优先级。
S906，S-GW将该业务数据以及业务数据的优先级发送给P-GW。
具体的，S-GW将业务数据封装到GTP-U数据包中发送给S-GW，其中，GTP-U数据包的包头中携带该业务数据的优先级。
S907，P-GW根据业务数据的优先级对业务数据进行计费。
P-GW可以生成计费数据P-GW CDR，并且该CDR中记录该业务数据的优先级。
实施例二
基于针对上述NB-IoT业务的服务质量需求分析，本发明实施例提出了业务数据传输方法，网络侧将终端的第二业务授权信息发送给终端，所述第二业务授权信息用于指示允许所述终端传输业务数据所采用的业务数据的业务类型和/或优先级，从而终端基于该第二业务授权信息确定发送的业务数据的信息，所述业务数据的信息包括所述业务数据的业务类型和所述业务数据的优先级中的至少一种，并将所述业务数据的信息通知到基站，从而基站基于业务数据的信息对传输业务数据提供服务。如图10所示，该方法包括：
S1001，终端发送请求消息给移动管理实体，所述请求消息包含传输方式指示信息，所述传输方式指示信息用于指示终端采用非接入层NAS信令消息传输业务数据。
S1002，所述移动管理实体接收终端发送的所述请求消息。
S1003，若所述移动管理实体根据所述请求消息确定所述终端通过非接入层NAS信令消息传输所述业务数据，则所述移动管理实体根据所述终端的签约信息，确定所述终端的第二业务授权信息。
所述第二业务授权信息包括用于指示允许所述终端传输业务数据所采用的业务类型和/或优先级的信息。
S1004，所述移动管理实体将所述第二业务授权信息发送给所述终端。
S1005，所述终端接收所述移动管理实体发送的所述第二业务授权信息。
S1006，所述终端根据所述第二业务授权信息，确定所述业务数据的信息。
所述业务数据的信息包括所述业务数据的业务类型和所述业务数据的优先级中的至少一种。
S1007，所述终端将所述业务数据的信息发送给所述接入网设备。
可选地，在终端向网络发起附着请求消息时，移动管理实体向HSS获取终端的签约信息。
其中，签约信息中可以包括允许终端发送的业务数据的优先级和/或业务数据的业务类型。移动管理实体将允许终端发送的业务数据的优先级和/或业 务数据的业务类型生成第二业务授权信息发送给终端，从而终端确定被允许发送的业务数据的业务类型和/或优先级，从而在接收到应用层请求发送的业务数据时，基于第二业务授权信息设置该业务数据的优先级和/或业务数据的业务类型，避免低优先级终端以高优先级发送业务数据；或者，
签约信息中可以包括允许终端发送的业务数据的优先级以及第二配额信息，所述第二配额信息用于指示在特定时间内允许发送所述优先级的业务数据的数量。这里优先级为高优先级。数量可以是业务数据的流量或者发送业务数据的次数等。移动管理实体将允许终端发送的业务数据的优先级以及第二配额信息生成第二业务授权信息发送给终端，从而终端确定发送的高优先级的业务数据的数量未达到第二配额信息时，可以以高优先级发送业务数据，若确定发送的高优先级的业务数据的数量达到第二配额信息时，只能以低优先级发送业务数据，从而避免低优先级终端过度使用高优先级发送业务数据；或者，
签约信息中可以包括允许终端发送的业务数据的业务类型为例外报告和第一配额信息，所述配额信息用于指示在特定时间内允许发送业务类型为例外报告的业务数据的数量。移动管理实体将允许终端发送的业务数据的业务类型以及第一配额信息生成第二业务授权信息发送给终端，从而终端确定发送的业务类型为例外报告的业务数据的数量未达到第一配额信息时，可以以例外报告发送业务数据，若终端确定发送的业务类型为例外报告的业务数据的数量达到第二配额信息时，只能以周期性报告发送业务数据，从而避免低优先级终端(以周期性报告为主的终端)过度使用高优先级发送业务数据。
下面以EPS系统为例对上述实施例二进行具体说明，如图11所示。其中，接入网设备为基站、终端称之为UE，移动管理实体为MME、网关包括S-GW以及P-GW。
S1101，UE向移动管理实体发送请求消息，所述请求消息包含传输方式指示信息，所述传输方式指示信息用于指示终端采用非接入层NAS信令消息传输业务数据。具体的UE在发起附着请求(Attach Request)时，将传输方 式指示信息发送给移动管理实体。
S1102，MME在接收到请求消息后，从HSS获取UE的签约信息，并基于签约信息确定第二业务授权信息。所述第二业务授权信息包括用于指示允许所述终端传输业务数据所采用的业务类型和/或优先级的信息；所述第二业务授权信息还可以包括第一配额信息，所述第一配额信息用于指示在特定时间内被允许发送所述业务类型的业务数据的数量。所述第二业务授权信息还可以包括第二配额信息，所述配额信息用于指示在特定时间内允许发送所述优先级的业务数据的数量。
即确定该UE是否可以发送高优先级的业务数据或者发送例外报告，以及允许发送的数量。
S1103，MME通过附着接受(Attach Accept)消息将第二业务授权信息通知给UE。
S1104，应用层请求以高优先级发送业务数据或者发送例外报告时，UE基于第二业务授权信息确定业务数据的信息。业务数据的信息包括业务数据的业务类型和业务数据的优先级中的至少一种。
例如，第二业务授权信息指示允许发送高优先级的业务数据的数量，则UE确定发送的高优先级的业务数据的数量未达到允许的数量时，则可以以高优先级发送业务数据，若达到允许的数量时，则以低优先级发送业务数据。
S1105，UE向基站发起RRC连接建立请求消息，并基于确定的所述业务数据的信息设置RRC连接建立原因值。
S1106，基站基于所述RRC建立原因值为UE传输业务数据分配传输资源。
从而UE基于基站分配的传输资源通过NAS信令消息将业务数据发送给基站。
S1107，基站在接收到UE发送的业务数据后，将该业务数据转发给MME，并通知MME该业务数据的信息。
S1108，MME在接收到业务数据以及该业务数据的信息后，将业务数据以及该业务数据的信息发送给S-GW。
具体的，MME将业务数据封装到用户层面的GPRS隧道协议(英文：GPRS Tunnel Protocol User Plane，简称：GTP-U)数据包中发送给S-GW，其中，GTP-U数据包的包头中携带该业务数据的信息。
S1109，S-GW根据该业务数据的信息对该业务数据进行计费。S-GW可以生成计费数据S-GW计费数据记录CDR，并且该CDR中记录该业务数据的信息。
S1110，S-GW将该业务数据以及该业务数据的信息发送给P-GW，。
具体的，S-GW将业务数据封装到GTP-U数据包中发送给S-GW，其中，GTP-U数据包的包头中携带该业务数据的信息。
S1111，P-GW根据该业务数据的信息对业务数据进行计费。
P-GW可以生成计费数据P-GW CDR，并且该CDR中记录该业务数据的QoS信息。
本发明提供的方案，MME在确定终端采用非接入层NAS信令消息传输业务数据时，将终端的第二业务授权信息发送给终端，从而终端基于该第二业务授权信息确定发送的业务数据的信息，并将所述业务数据的信息通知到基站，从而基站基于业务数据的信息对传输业务数据提供服务。另外，基站将业务数据的信息发送给P-GW以及S-GW，从而P-GW以及S-GW基于业务数据的信息对业务数据进行计费。通过计费控制，高优先级的业务数据传输以及低优先级的业务数据传输采用不同计费标准，避免了低优先级终端(以周期性报告为主的中终端)过度通过高优先级来传输业务数据，从而减少由于多数终端均采用高优先级的发送业务数据造成的数据传输拥塞。
实施例三
基于针对上述NB-IoT业务的服务质量需求分析，本发明实施例提出了业务数据传输方法，移动管理实体向接入网设备提供下行的业务数据的信息，业务数据的信息包括业务数据的优先级和/或业务数据的业务类型，从而接入网设备基于业务数据的信息对业务数据进行传输资源管理。如图12所示，该方法包括：
S1201，移动管理实体接收网关发送的终端的业务数据。
具体的，移动管理实体在EPS系统为MME，网关为S-GW或P-GW。
S1202，所述移动管理实体获取所述业务数据的第一信息，所述第一信息包括业务类型和优先级中的至少一种。
S1203，所述移动管理实体向接入网设备发送NAS信令消息，所述NAS信令消息携带所述业务数据。
S1204，所述移动管理实体将所述业务数据以及业务数据的第一信息发送给接入网设备。
S1205，所述接入网设备在接收到所述业务数据的第一信息后，基于所述业务数据的第一信息对所述业务数据进行传输资源管理。
具体的，基于该第一信息对所述业务数据进行传输资源管理可以是基于第一信息为待发送的业务数据分配传输资源，即网络资源。比如，终端待传输的业务数据的业务类型为例外报告，例外报告对传输时延有要求，因此接入网设备为该业务数据分配的网络资源要满足例外报告的时延要求。
可选地，所述移动管理实体获取所述业务数据的第一信息，可以通过如下方式实现：
第一种实现方式：
所述移动管理实体根据所述终端的签约信息，确定所述业务数据的第一信息。
其中，签约信息中可以包括允许终端发送的业务数据的优先级和/或业务数据的业务类型。比如：若签约信息中包括允许终端发送的业务数据的业务类型为周期性报告，则移动管理实体确定第一信息中包括的所述业务数据的业务类型为周期性报告；或者若签约信息中包括允许终端发送的业务数据的业务类型为例外报告，则移动管理实体确定第一信息包括的所述业务数据的业务类型为例外报告。
第二种实现方式：
在业务数据的数据包的包头中携带所述业务数据的第一信息，则所述移 动管理实体从所述业务数据的数据包的包头中获取所述业务数据的第一信息。
具体的，网关可以从业务数据的携带的DSCP(IPv4)或者ToS(IPv6)中获取所述业务数据的第一信息。
本发明实施例中接入网设备在EPS系统中为eNB，网关在EPS系统中为P-GW或者S-GW，移动管理实体在EPS系统为MME。
下面结合具体应用场景(本发明以EPS系统为例)对上述实施例三进行具体说明，如图12所示。
S1301，P-GW向S-GW发送终端的业务数据；
S1302，S-GW在接收到所述业务数据后，将所述业务数据发送给MME；
S1303，MME接收到所述业务数据后，从HSS获取所述业务数据的第一信息。在业务数据的数据包的包头中携带第一信息时，所述MME还可以从业务数据的数据包的包头获取业务数据的第一信息。在本实施例中第一信息以业务数据的优先级为例。
其中，业务数据的数据包的包头中携带差分服务代码点(英文：Differentiated Services Code Point，简称：DSCP)或者服务类型(英文：Type of Service，简称：ToS)，DSCP或者ToS中包括第一信息
S1304，MME向基站发送所述业务数据以及业务数据的优先级。
其中，MME确定业务数据的优先级生成ARP或者其他优先级参数，并在发送下行NAS传输(Downlink NAS Transport)消息时，将业务数据以及对应的优先级参数携带在Downlink NAS Transport消息发送给基站。
S1305，基站在接收到所述业务数据以及业务数据的优先级后，基于所述业务数据的优先级对业务数据进行传输资源管理。
具体的，基站基于业务数据的优先级为业务数据分配网络资源，从而基站通过分配的网络资源将业务数据发送给终端。
本发明实施例还提供了一种接入网设备，如图14所示，该接入网设备包括：
确定单元1401，用于确定终端待发送的业务数据的第一信息，所述第一信息包括业务类型和优先级中的至少一种；
接收单元1402，用于接收所述终端通过非接入层NAS信令消息发送的所述业务数据；
发送单元1403，用于将所述接收单元1402接收到的所述业务数据以及所述确定单元1401确定的所述第一信息发送给网关，以使得所述网关根据所述第一信息对所述业务数据进行计费。
在一种可能的设计中，所述接入网设备还可以包括：管理单元1404，用于在所述确定单元1401确定终端待发送的业务数据的第一信息之后，所述接收单元1402接收所述终端通过非接入层NAS信令消息发送的所述业务数据之前，根据所述第一信息对所述业务数据进行传输资源管理。
在一种可能的设计中，所述确定单元1401，具体用于在所述接收单元1402接收到终端发送的所述第一信息，则确定所述第一信息。
在一种可能的设计中，所述接收单元1402，还用于接收所述终端发送的第二信息，所述第二信息包括所述终端请求传输所述业务数据所采用的业务类型和/或优先级；
所述发送单元1403，还用于将所述第二信息发送给移动管理实体；
所述接收单元1402，还用于接收所述移动管理实体发送的第一业务授权信息，所述第一业务授权信息用于指示允许所述终端传输所述业务数据所采用的业务类型和/或优先级；
所述确定单元1401，具体用于根据所述第一业务授权信息，确定所述第一信息。
在一种可能的设计中，所述第一业务授权信息包括指示信息，所述指示信息用于指示允许所述第二信息。
本发明实施例中对单元的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，另外，在本发明各个实施例中的各功能单元可以集成在一个处理器中，也可以是单独物理存在，也可以两个或两个 以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。
其中，在集成的单元采用硬件的形式实现时，如图15所示，可以包括接收器1501、处理器1502以及通信接口1503。还包括存储器1504。所述存储器1504，用于存储所述处理器1502执行的程序代码。发送单元1403对应的实体硬件可以为通信接口1503，接收单元1402对应的实体硬件可以为接收器1501，确定单元1401以及管理单元1404对应的实体硬件可以为处理器1502。
处理器1502，可以是一个中央处理单元(英文：central processing unit，简称CPU)，或者为数字处理单元等等。处理器1502通过接收器1501接收终端发送的消息以及通过通信接口1503与网关以及移动管理实体之间进行收发消息。
本发明实施例中不限定上述接收器1501、处理器1502、通信接口1503以及存储器1504之间的具体连接介质。本发明实施例在图15中以接收器1501、处理器1502、通信接口1503以及存储器1504之间通过总线1505连接，总线在图15中以粗线表示，其它部件之间的连接方式，仅是进行示意性说明，并不引以为限。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图15中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
存储器1504可以是易失性存储器(英文：volatile memory)，例如随机存取存储器(英文：random-access memory，缩写：RAM)；存储器1504也可以是非易失性存储器(英文：non-volatile memory)，例如只读存储器(英文：read-only memory，缩写：ROM)，快闪存储器(英文：flash memory)，硬盘(英文：hard disk drive，缩写：HDD)或固态硬盘(英文：solid-state drive，缩写：SSD)、或者存储器1504是能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器1504可以是上述存储器的组合。
处理器1502，用于确定终端待发送的业务数据的第一信息，所述第一信 息包括业务类型和优先级中的至少一种；
接收器1501，用于接收所述终端通过非接入层NAS信令消息发送的所述业务数据；
通信接口1503，用于将所述业务数据以及所述第一信息发送给网关，以使得所述网关根据所述第一信息对所述业务数据进行计费。
在一种可能的设计中，在所述处理器1502确定终端待发送的业务数据的第一信息之后，所述接收器1501接收所述终端通过NAS信令消息发送的所述业务数据之前，所述处理器1502，还用于根据所述第一信息，对所述业务数据进行传输资源管理。
在一种可能的设计中，所述接收器1501，还用于接收终端发送的所述第一信息。
在一种可能的设计中，所述接收器1501，还用于接收所述终端发送的第二信息，所述第二信息包括所述终端请求传输所述业务数据所采用的业务类型和/或优先级；
所述通信接口1503，还用于将所述第二信息发送给移动管理实体；
所述通信接口1503，还用于接收所述移动管理实体发送的第一业务授权信息，所述第一业务授权信息用于指示允许所述终端传输所述业务数据所采用的业务类型和/或优先级；
所述处理器1502，具体用于根据所述第一业务授权信息，确定所述第一信息。
在一种可能的设计中，所述第一业务授权信息包括指示信息，所述指示信息用于指示允许所述第二信息。
需要指出的是，图14或15所示实施例中的接入网设备可以用于执行上述方法实施例一或实施例一的各实施场景中接入网设备或基站的操作步骤，不再一一赘述。
本发明实施例提供了移动管理实体，如图16所示，所述移动管理实体包括：
接收单元1601，用于接收非接入层NAS信令消息，所述NAS信令消息携带终端的业务数据；
获取单元1602，用于获取所述接收单元1601接收到的所述业务数据的第一信息，所述第一信息包括业务类型和优先级中的至少一种；
发送单元1603，用于将所述业务数据以及所述第一信息发送给网关，以使得所述网关对所述业务数据进行计费。
在一种可能的设计中，所述获取单元1602，具体用于在所述接收单元1601接收到接入网设备发送的所述第一信息，则获取到所述第一信息。
在一种可能的设计中，所述接收单元1601在接收所述接入网设备发送的所述第一信息之前，还用于接收所述接入网设备发送的第二信息，所述第二信息包括所述终端请求传输所述业务数据所采用的业务类型和/或优先级；
所述移动管理实体还包括授权单元1604，用于根据所述终端的签约信息，对所述第二信息进行授权得到第一业务授权信息，所述第一业务授权信息用于指示允许所述终端传输所述业务数据所采用的业务类型和/或优先级；
所述发送单元1603，还用于将所述第一业务授权信息发送给所述接入网设备，以使得所述接入网设备基于所述第一业务授权信息确定所述第一信息。
在一种可能的设计中，所述获取单元1602，具体用于在所述接收单元1601接收到所述终端发送的所述第一信息时，则获取到所述第一信息。
本发明实施例中对单元的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，另外，在本发明各个实施例中的各功能单元可以集成在一个处理器中，也可以是单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。
其中，在集成的单元采用硬件的形式实现时，如图17所示，可以包括通信接口1701、处理器1702以及存储器1703。所述存储器1703，用于存储所述处理器1702执行的程序代码。发送单元1603对应的实体硬件可以为通信接口1701，接收单元1601对应的实体硬件可以为通信接口1701，获取单元 1602以及授权单元1604对应的实体硬件可以为处理器1702。
处理器1702，可以是一个中央处理单元(英文：central processing unit，简称CPU)，或者为数字处理单元等等。处理器1702通过通信接口1701接收和发送消息。
本发明实施例中不限定上述通信接口1701、处理器1702以及存储器1703之间的具体连接介质。本发明实施例在图17中以通信接口1701、处理器1702以及存储器1703之间通过总线1704连接，总线在图17中以粗线表示，其它部件之间的连接方式，仅是进行示意性说明，并不引以为限。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图17中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
存储器1703可以是volatile memory，例如RAM；存储器1703也可以是non-volatile memory，例如ROM，flash memory、HDD、SSD，或者存储器1703是能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器1703可以是上述存储器的组合。
通信接口1701，用于接收非接入层NAS信令消息，所述NAS信令消息携带终端的业务数据；
处理器1702，用于获取所述业务数据的第一信息，所述第一信息包括所述业务数据的业务类型和所述业务数据的优先级中的至少一种；
通信接口1701，用于将所述业务数据以及所述第一信息发送给网关，以使得所述网关对所述业务数据进行计费。
在一种可能的设计中，所述通信接口1701，还用于接收接入网设备发送的所述第一信息。
在一种可能的设计中，所述通信接口1701，在接收所述接入网设备发送的所述第一信息之前，还用于接收所述接入网设备发送的第二信息，所述第二信息包括所述终端请求传输所述业务数据所采用的业务类型和/或优先级；
所述处理器1702，还用于根据所述终端的签约信息，对所述第二信息进 行授权得到第一业务授权信息，所述第一业务授权信息用于指示允许所述终端传输所述业务数据所采用的业务类型和/或优先级；
所述通信接口1701，还用于将所述第一业务授权信息发送给所述接入网设备，以使得所述接入网设备基于所述第一业务授权信息确定所述第一信息。
在一种可能的设计中，所述通信接口1701，还用于接收所述终端发送的所述第一信息。
需要指出的是，图16或17所示实施例中的移动管理实体可以用于执行上述方法实施例一或实施例一的各实施场景中移动管理实体或MME的操作步骤，不再一一赘述。
本发明实施例还提供了一种网关，如图18所示，该网关包括：
接收单元1801，用于接收移动管理实体发送的终端的业务数据和所述业务数据的第一信息，所述第一信息包括业务类型和优先级中的至少一种；
计费单元1802，用于根据所述接收单元1801接收到的所述第一信息，对所述业务数据进行计费。
本发明实施例中对单元的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，另外，在本发明各个实施例中的各功能单元可以集成在一个处理器中，也可以是单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。
其中，在集成的单元采用硬件的形式实现时，如图19所示，可以包括通信接口1901、处理器1902以及存储器1903。所述存储器1903，用于存储所述处理器1902执行的程序代码。接收单元1801对应的实体硬件可以为通信接口1901，计费单元1802对应的实体硬件可以为处理器1902。
处理器1902，可以是一个中央处理单元(英文：central processing unit，简称CPU)，或者为数字处理单元等等。处理器1902通过通信接口1901接收和发送消息。
本发明实施例中不限定上述通信接口1901、处理器1902以及存储器1903 之间的具体连接介质。本发明实施例在图19中以通信接口1901、处理器1902以及存储器1903之间通过总线1904连接，总线在图19中以粗线表示，其它部件之间的连接方式，仅是进行示意性说明，并不引以为限。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图19中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
存储器1903可以是volatile memory，例如RAM；存储器1903也可以是non-volatile memory，例如ROM，flash memory、HDD、SSD，或者存储器1903是能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器1903可以是上述存储器的组合。
通信接口1901，用于接收移动管理实体发送的终端的业务数据和所述业务数据的第一信息，所述第一信息包括业务类型和优先级中的至少一种；
处理器1902，用于根据所述通信接口1901接收到的所述第一信息，对所述业务数据进行计费。
需要指出的是，图18或19所示实施例中的网关可以用于执行上述方法实施例一或实施例一的各实施场景中网关或S-GW或P-GW的操作步骤，不再一一赘述。
本发明实施例还提供了另一种接入网设备，如图20所示，所述接入网设备包括：
接收单元2001，用于接收移动管理实体通过非接入层NAS信令消息发送的业务数据；以及接收所述移动管理实体发送的所述业务数据的信息，所述业务数据的信息包括所述业务数据的业务类型和所述业务数据的优先级中的至少一种；
管理单元2002，用于根据所述接收单元2001接收到的所述业务数据的信息，对所述业务数据进行传输资源管理。
本发明实施例中对单元的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，另外，在本发明各个实施例中的各功能 单元可以集成在一个处理器中，也可以是单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。
其中，在集成的单元采用硬件的形式实现时，如图21所示，可以包括通信接口2101、处理器2102。还包括存储器2103。所述存储器2103，用于存储所述处理器2102执行的程序代码。接收单元2001对应的实体硬件可以为通信接口2101，管理单元2002对应的实体硬件可以为处理器2102。通信接口2101用于向终端发送数据或者消息。
处理器2102，可以是一个CPU，或者为数字处理单元等等。处理器2102通过通信接口2101接收以及发送消息。
本发明实施例中不限定上述通信接口2101、处理器2102、以及存储器2103之间的具体连接介质。本发明实施例在图21中以通信接口2101、处理器2102、以及存储器2103之间通过总线2104连接，总线在图21中以粗线表示，其它部件之间的连接方式，仅是进行示意性说明，并不引以为限。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图21中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
存储器2103可以是volatile memory，例如RAM；存储器2103也可以是non-volatile memory，例如ROM，flash memory、HDD、SSD，或者存储器2103是能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器2103可以是上述存储器的组合。
通信接口2101，用于接收移动管理实体通过非接入层NAS信令消息发送的业务数据；以及接收所述移动管理实体发送的所述业务数据的信息，所述业务数据的信息包括所述业务数据的业务类型和所述业务数据的优先级中的至少一种；处理器2102，用于根据所述业务数据的信息，对所述业务数据进行传输资源管理。
需要指出的是，图20或21所示实施例中的接入网设备可以用于执行上 述方法实施例三或实施例三的各实施场景中接入网设备或基站的操作步骤，不再一一赘述。
本发明实施例提供了一种移动管理实体，如图22所示，该移动管理实体包括：
接收单元2201，用于接收网关发送的终端的业务数据；
获取单元2202，用于获取所述接收单元2202接收到的所述业务数据的第一信息，所述第一信息包括所述业务数据的业务类型和所述业务数据的优先级中的至少一种；
发送单元2203，用于向接入网设备发送非接入层NAS信令消息，所述NAS信令消息携带所述获取单元2202获取到的所述业务数据；将所述第一信息发送给所述接入网设备，以使得所述接入网设备根据所述第一信息对所述业务数据进行传输资源管理。
在一种可能的设计中，所述获取单元2202，具体用于根据所述终端的签约信息，确定所述第一信息；或者，
所述业务数据的数据包的包头中携带所述第一信息，所述获取单元2202从所述业务数据的数据包的包头中获取所述第一信息。
本发明实施例中对单元的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，另外，在本发明各个实施例中的各功能单元可以集成在一个处理器中，也可以是单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。
其中，在集成的单元采用硬件的形式实现时，如图23所示，可以包括通信接口2301、处理器2302、、存储器2303。所述存储器2303，用于存储所述处理器2302执行的程序代码。接收单元2201对应的实体硬件可以为通信接口2301，获取单元2202对应的实体硬件可以为处理器2302。发送单元2203对应的实体硬件可以为通信接口2301。
处理器2302，可以是一个CPU，或者为数字处理单元等等。处理器2302 通过通信接口2301接收以及发送消息。
本发明实施例中不限定上述通信接口2301、处理器2302以及存储器2303之间的具体连接介质。本发明实施例在图23中以通信接口2301、处理器2302、存储器2303之间通过总线2304连接，总线在图23中以粗线表示，其它部件之间的连接方式，仅是进行示意性说明，并不引以为限。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图23中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
存储器2303可以是volatile memory，例如RAM；存储器2303也可以是non-volatile memory，例如ROM，flash memory、HDD、SSD，或者存储器2303是能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器2303可以是上述存储器的组合。
通信接口2301，用于接收网关发送的终端的业务数据；
处理器2302，用于获取所述业务数据的第一信息，所述第一信息包括所述业务数据的业务类型和所述业务数据的优先级中的至少一种；
通信接口2301，用于向接入网设备发送非接入层NAS信令消息，所述NAS信令消息携带所述业务数据；并将所述第一信息发送给所述接入网设备，以使得所述接入网设备根据所述第一信息对所述业务数据进行传输资源管理。
在一种可能的设计中，所述处理器2302具体用于根据所述终端的签约信息，确定所述第一信息；或者，
所述业务数据的数据包的包头中携带所述第一信息，所述处理器2302具体用于从所述业务数据的数据包的包头中获取所述第一信息。
需要指出的是，图22或23所示实施例中的移动管理实体可以用于执行上述方法实施例三或实施例三的各实施场景中移动管理实体或MME的操作步骤，不再一一赘述。
本发明实施例提供了一种移动管理实体，如图24所示，该移动管理实体包括：
接收单元2401，用于接收请求消息，所述请求消息包含传输方式指示信息，所述传输方式指示信息用于指示终端采用非接入层NAS信令消息传输业务数据；
确定单元2402，用于在根据所述请求消息确定所述终端通过非接入层NAS信令消息传输所述业务数据，则根据所述终端的签约信息，确定所述终端的第二业务授权信息，所述第二业务授权信息包括用于指示允许所述终端传输业务数据所采用的业务类型和/或优先级的信息；
发送单元2403，用于将所述确定单元2402确定的所述第二业务授权信息发送给所述终端。
在一种可能的设计中，所述第二业务授权信息还包括第一配额信息，所述第一配额信息用于指示在特定时间内允许发送所述业务类型的业务数据的数量。
在一种可能的设计中，所述业务授权信息还包括第二配额信息，所述第二配额信息用于指示在特定时间内允许发送的所述优先级的业务数据的数量。
本发明实施例中对单元的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，另外，在本发明各个实施例中的各功能单元可以集成在一个处理器中，也可以是单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。
其中，在集成的单元采用硬件的形式实现时，如图25所示，可以包括通信接口2501、处理器2502以及存储器2503。所述存储器2503，用于存储所述处理器2502执行的程序代码。接收单元2401对应的实体硬件可以为通信接口2501，确定单元2402对应的实体硬件可以为处理器2502。发送单元2403对应的实体硬件可以为通信接口2501。
处理器2502，可以是一个CPU，或者为数字处理单元等等。处理器2502通过通信接口2501接收消息以及通过通信接口2501发送消息。
本发明实施例中不限定上述通信接口2501、处理器2502以及存储器2503之间的具体连接介质。本发明实施例在图25中以通信接口2501、处理器2502以及存储器2503之间通过总线2504连接，总线在图25中以粗线表示，其它部件之间的连接方式，仅是进行示意性说明，并不引以为限。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图25中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
存储器2503可以是volatile memory，例如RAM；存储器2503也可以是non-volatile memory，例如ROM，flash memory、HDD、SSD，或者存储器2503是能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器2503可以是上述存储器的组合。
通信接口2501，用于接收请求消息，所述请求消息包含传输方式指示信息，所述传输方式指示信息用于指示终端采用非接入层NAS信令消息传输业务数据；
处理器2502，用于在根据所述请求消息确定所述终端通过非接入层NAS信令消息传输所述业务数据时，则根据所述终端的签约信息，确定所述终端的第二业务授权信息，所述第二业务授权信息包括用于指示允许所述终端传输业务数据所采用的业务类型和/或优先级的信息；
通信接口2501，还用于将所述第二业务授权信息发送给所述终端。
在一种可能的设计中，所述第二业务授权信息还包括第一配额信息，所述第一配额信息用于指示在特定时间内允许发送所述业务类型的业务数据的数量。
在一种可能的设计中，所述业务授权信息还包括第二配额信息，所述第二配额信息用于指示在特定时间内允许发送的所述优先级的业务数据的数量。
需要指出的是，图24或25所示实施例中的移动管理实体可以用于执行上述方法实施例二或实施例二的各实施场景中移动管理实体或MME的操作步骤，不再一一赘述。
本发明实施例提供了一种终端，如图26所示，该终端包括：
发送单元2601，用于发送请求消息给移动管理实体，所述请求消息包含传输方式指示信息，所述传输方式指示信息用于指示终端采用非接入层NAS信令消息传输业务数据；
接收单元2602，用于接收所述移动管理实体发送的第二业务授权信息，所述第二业务授权信息包括用于指示允许所述终端传输业务数据所采用的业务类型和/或优先级的信息；
确定单元2603，用于根据所述接收单元2602接收到的所述第二业务授权信息，确定所述业务数据的信息，所述业务数据的信息包括所述业务数据的业务类型和所述业务数据的优先级中的至少一种；
所述发送单元2601，还用于将所述确定单元2603确定的所述业务数据的信息发送给所述接入网设备。
在一种可能的设计中，所述第二业务授权信息还包括第一配额信息，所述第一配额信息用于指示在特定时间内被允许发送所述业务类型的业务数据的数量。
在一种可能的设计中，所述第二业务授权信息还包括第二配额信息，所述配额信息用于指示在特定时间内允许发送所述优先级的业务数据的数量。
本发明实施例中对单元的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，另外，在本发明各个实施例中的各功能单元可以集成在一个处理器中，也可以是单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。
其中，在集成的单元采用硬件的形式实现时，如图27所示，可以包括接收器2701、处理器2702以及发射器2703。还包括存储器2704。所述存储器 2704，用于存储所述处理器2702执行的程序代码。接收单元2602对应的实体硬件可以为接收器2701，确定单元2603对应的实体硬件可以为处理器2702。发送单元2601对应的实体硬件可以为发射器2703。
处理器2702，可以是一个CPU，或者为数字处理单元等等。处理器2702通过接收器2701接收消息以及通过发射器2703发送消息。
本发明实施例中不限定上述接收器2701、处理器2702、发射器2703以及存储器2704之间的具体连接介质。本发明实施例在图27中以接收器2701、处理器2702、发射器2703以及存储器2704之间通过总线2705连接，总线在图27中以粗线表示，其它部件之间的连接方式，仅是进行示意性说明，并不引以为限。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图27中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
存储器2704可以是volatile memory，例如RAM；存储器2704也可以是non-volatile memory，例如ROM，flash memory、HDD、SSD，或者存储器2704是能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器2704可以是上述存储器的组合。
发射器2703，用于发送请求消息给移动管理实体，所述请求消息包含传输方式指示信息，所述传输方式指示信息用于指示终端采用非接入层NAS信令消息传输业务数据；
接收器2701，用于接收所述移动管理实体发送的第二业务授权信息，所述第二业务授权信息包括用于指示允许所述终端传输业务数据所采用的业务类型和/或优先级的信息；
处理器2702，用于根据所述第二业务授权信息，确定所述业务数据的信息，所述业务数据的信息包括所述业务数据的业务类型和所述业务数据的优先级中的至少一种；
所述发射器2703，还用于将所述业务数据的信息发送给所述接入网设备。
在一种可能的设计中，所述第二业务授权信息还包括第一配额信息，所 述第一配额信息用于指示在特定时间内被允许发送所述业务类型的业务数据的数量。
在一种可能的设计中，所述第二业务授权信息还包括第二配额信息，所述配额信息用于指示在特定时间内允许发送所述优先级的业务数据的数量。
需要指出的是，图26或27所示实施例中的终端可以用于执行上述方法实施例二或实施例二的各实施场景中终端或UE的操作步骤，不再一一赘述。
本领域内的技术人员应明白，本发明的实施例可提供为方法、系统、或计算机程序产品。因此，本发明可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本发明可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本发明是参照根据本发明的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的设备。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步 骤。
尽管已描述了本发明的优选实施例，但本领域内的技术人员一旦得知了基本创造性概念，则可对这些实施例做出另外的变更和修改。所以，所附权利要求意欲解释为包括优选实施例以及落入本发明范围的所有变更和修改。
显然，本领域的技术人员可以对本发明进行各种改动和变型而不脱离本发明的精神和范围。这样，倘若本发明的这些修改和变型属于本发明权利要求及其等同技术的范围之内，则本发明也意图包含这些改动和变型在内。

Claims (36)

  1. 一种业务数据传输方法，其特征在于，包括：
    接入网设备确定终端待发送的业务数据的第一信息，所述第一信息包括业务类型和优先级中的至少一种；
    所述接入网设备接收所述终端通过非接入层NAS信令消息发送的所述业务数据；
    所述接入网设备将所述业务数据以及所述第一信息通过移动管理实体发送给网关，以使得所述网关根据所述第一信息对所述业务数据进行计费。
  2. 如权利要求1所述的方法，其特征在于，在所述接入网设备确定终端待发送的业务数据的第一信息之后，所述接入网设备接收所述终端通过非接入层NAS信令消息发送的所述业务数据之前，还包括：
    所述接入网设备根据所述第一信息，对所述业务数据进行传输资源管理。
  3. 如权利要求1或2所述的方法，其特征在于，所述接入网设备确定终端待发送的业务数据的第一信息，包括：
    所述接入网设备接收所述终端发送的所述第一信息。
  4. 如权利要求1或2所述的方法，其特征在于，所述接入网设备确定终端待发送的业务数据的第一信息，包括：
    所述接入网设备接收所述终端发送的第二信息，所述第二信息包括所述终端请求传输所述业务数据所采用的业务类型和/或优先级；
    所述接入网设备将所述第二信息发送给移动管理实体；
    所述接入网设备接收所述移动管理实体发送的第一业务授权信息，所述第一业务授权信息用于指示允许所述终端传输所述业务数据所采用的业务类型和/或优先级；
    所述接入网设备根据所述第一业务授权信息，确定所述第一信息。
  5. 如权利要求4所述的方法，其特征在于，所述第一业务授权信息包括指示信息，所述指示信息用于指示允许所述第二信息。
  6. 一种业务数据传输方法，其特征在于，包括：
    移动管理实体接收非接入层NAS信令消息，所述NAS信令消息携带终端的业务数据；
    所述移动管理实体获取所述业务数据的第一信息，所述第一信息包括业务类型和优先级中的至少一种；
    所述移动管理实体将所述业务数据以及所述第一信息发送给网关，以使得所述网关对所述业务数据进行计费。
  7. 如权利要求6所述的方法，其特征在于，所述移动管理实体获取所述业务数据的第一信息，包括：
    所述移动管理实体接收接入网设备发送的所述第一信息；或者，
    所述移动管理实体接收所述终端通过NAS信令消息发送的所述第一信息。
  8. 如权利要求6或7所述的方法，其特征在于，所述移动管理实体接收所述接入网设备发送的所述第一信息之前，还包括：
    所述移动管理实体接收所述接入网设备发送的第二信息，所述第二信息包括所述终端请求传输所述业务数据所采用的业务类型和/或优先级；
    所述移动管理实体根据所述终端的签约信息，对所述第二信息进行授权得到第一业务授权信息，所述第一业务授权信息用于指示允许所述终端传输所述业务数据所采用的业务类型和/或优先级；
    所述移动管理实体将所述第一业务授权信息发送给所述接入网设备，以使得所述接入网设备基于所述第一业务授权信息确定所述第一信息。
  9. 一种业务数据传输方法，其特征在于，包括：
    网关接收移动管理实体发送的终端的业务数据和所述业务数据的第一信息，所述第一信息包括业务类型和优先级中的至少一种；
    所述网关根据所述第一信息，对所述业务数据进行计费。
  10. 一种业务数据传输方法，其特征在于，包括：
    接入网设备接收移动管理实体通过非接入层NAS信令消息发送的业务数 据；
    所述接入网设备接收所述移动管理实体发送的所述业务数据的信息，所述业务数据的信息包括业务类型和优先级中的至少一种；
    所述接入网设备根据所述业务数据的信息，对所述业务数据进行传输资源管理。
  11. 一种业务数据传输方法，其特征在于，包括：
    移动管理实体接收网关发送的终端的业务数据；
    所述移动管理实体获取所述业务数据的第一信息，所述第一信息包括业务类型和优先级中的至少一种；
    所述移动管理实体向接入网设备发送非接入层NAS信令消息，所述NAS信令消息携带所述业务数据；
    所述移动管理实体将所述第一信息发送给所述接入网设备，以使得所述接入网设备根据所述第一信息对所述业务数据进行传输资源管理。
  12. 如权利要求11所述的方法，其特征在于，所述移动管理实体获取所述业务数据的第一信息，包括：
    所述移动管理实体根据所述终端的签约信息，确定所述第一信息；或者，
    所述业务数据的数据包的包头中携带所述第一信息，所述移动管理实体从所述业务数据的数据包的包头中获取所述第一信息。
  13. 一种业务数据传输方法，其特征在于，包括：
    移动管理实体接收请求消息，所述请求消息包含传输方式指示信息，所述传输方式指示信息用于指示终端采用非接入层NAS信令消息传输业务数据；
    若所述移动管理实体根据所述请求消息确定所述终端通过非接入层NAS信令消息传输所述业务数据，则所述移动管理实体根据所述终端的签约信息，确定所述终端的第二业务授权信息，所述第二业务授权信息包括用于指示允许所述终端传输业务数据所采用的业务类型和/或优先级的信息；
    所述移动管理实体将所述第二业务授权信息发送给所述终端。
  14. 如权利要求13所述的方法，其特征在于，所述第二业务授权信息还包括第一配额信息，所述第一配额信息用于指示在特定时间内允许发送所述业务类型的业务数据的数量。
  15. 如权利要求13所述的方法，其特征在于，所述业务授权信息还包括第二配额信息，所述第二配额信息用于指示在特定时间内允许发送的所述优先级的业务数据的数量。
  16. 一种业务数据传输方法，其特征在于，包括：
    终端发送请求消息给移动管理实体，所述请求消息包含传输方式指示信息，所述传输方式指示信息用于指示终端采用非接入层NAS信令消息传输业务数据；
    所述终端接收所述移动管理实体发送的第二业务授权信息，所述第二业务授权信息包括用于指示允许所述终端传输业务数据所采用的业务类型和/或优先级的信息；
    所述终端根据所述第二业务授权信息，确定所述业务数据的信息，所述业务数据的信息包括所述业务数据的业务类型和所述业务数据的优先级中的至少一种；
    所述终端将所述业务数据的信息发送给所述接入网设备。
  17. 如权利要求16所述的方法，其特征在于，所述第二业务授权信息还包括第一配额信息，所述第一配额信息用于指示在特定时间内被允许发送所述业务类型的业务数据的数量。
  18. 如权利要求16所述的方法，其特征在于，所述第二业务授权信息还包括第二配额信息，所述配额信息用于指示在特定时间内允许发送所述优先级的业务数据的数量。
  19. 一种接入网设备，其特征在于，包括：
    处理器，用于确定终端待发送的业务数据的第一信息，所述第一信息包括业务类型和优先级中的至少一种；
    接收器，用于接收所述终端通过非接入层NAS信令消息发送的所述业务 数据；
    通信接口，用于将所述接收器接收到的所述业务数据以及所述处理器确定的所述第一信息通过移动管理实体发送给网关，以使得所述网关根据所述第一信息对所述业务数据进行计费。
  20. 如权利要求19所述的接入网设备，其特征在于，在所述处理器确定终端待发送的业务数据的第一信息之后，所述接收器接收所述终端通过非接入层NAS信令消息发送的所述业务数据之前，所述处理器，还用于根据所述第一信息，对所述业务数据进行传输资源管理。
  21. 如权利要求19或20所述的接入网设备，其特征在于，所述接收器，还用于接收所述终端发送的所述第一信息。
  22. 如权利要求19或20所述的接入网设备，其特征在于，所述接收器，还用于接收所述终端发送的第二信息，所述第二信息包括所述终端请求传输所述业务数据所采用的业务类型和/或优先级；
    所述通信接口，还用于将所述第二信息发送给移动管理实体；
    所述通信接口，还用于接收所述移动管理实体发送的第一业务授权信息，所述第一业务授权信息用于指示允许所述终端传输所述业务数据所采用的业务类型和/或优先级；
    所述处理器，具体用于根据所述第一业务授权信息，确定所述第一信息。
  23. 如权利要求22所述的接入网设备，其特征在于，所述第一业务授权信息包括指示信息，所述指示信息用于指示允许所述第二信息。
  24. 一种移动管理实体，其特征在于，包括：
    通信接口，用于接收非接入层NAS信令消息，所述NAS信令消息携带终端的业务数据；
    处理器，用于获取所述通信接口接收到的所述业务数据的第一信息，所述第一信息包括业务类型和优先级中的至少一种；
    所述通信接口，还用于将所述业务数据以及处理器获取的所述第一信息发送给网关，以使得所述网关对所述业务数据进行计费。
  25. 如权利要求24所述的移动管理实体，其特征在于，所述通信接口，还用于接收接入网设备发送的所述第一信息；或者，
    所述通信接口，还用于接收所述终端通过非接入层NAS信令消息发送的所述第一信息。
  26. 如权利要求25所述的移动管理实体，其特征在于，所述通信接口，在接收所述接入网设备发送的所述第一信息之前，还用于接收所述接入网设备发送的第二信息，所述第二信息包括所述终端请求传输所述业务数据所采用的业务类型和/或优先级；
    所述处理器，还用于根据所述终端的签约信息，对所述第二信息进行授权得到第一业务授权信息，所述第一业务授权信息用于指示允许所述终端传输所述业务数据所采用的业务类型和/或优先级；
    所述通信接口，还用于将所述第一业务授权信息发送给所述接入网设备，以使得所述接入网设备基于所述第一业务授权信息确定所述第一信息。
  27. 一种网关，其特征在于，包括：
    通信接口，用于接收移动管理实体发送的终端的业务数据和所述业务数据的第一信息，所述第一信息包括业务类型和优先级中的至少一种；
    处理器，用于根据所述通信接口接收到的所述第一信息，对所述业务数据进行计费。
  28. 一种接入网设备，其特征在于，包括：
    通信接口，用于接收移动管理实体通过非接入层NAS信令消息发送的业务数据；以及接收所述移动管理实体发送的所述业务数据的信息，所述业务数据的信息包括所述业务数据的业务类型和所述业务数据的优先级中的至少一种；
    处理器，用于根据所述业务数据的信息，对所述业务数据进行传输资源管理。
  29. 一种移动管理实体，其特征在于，包括：
    通信接口，用于接收网关发送的终端的业务数据；
    处理器，用于获取所述通信接口接收到的所述业务数据的第一信息，所述第一信息包括业务类型和优先级中的至少一种；
    所述通信接口，还用于向接入网设备发送非接入层NAS信令消息，所述NAS信令消息携带所述业务数据；并将所述处理器获取的所述第一信息发送给所述接入网设备，以使得所述接入网设备根据所述第一信息对所述业务数据进行传输资源管理。
  30. 如权利要求29所述的移动管理实体，其特征在于，所述处理器具体用于根据所述终端的签约信息，确定所述第一信息；或者，
    所述业务数据的数据包的包头中携带所述第一信息，所述处理器具体用于从所述业务数据的数据包的包头中获取所述第一信息。
  31. 一种移动管理实体，其特征在于，包括：
    通信接口，用于接收请求消息，所述请求消息包含传输方式指示信息，所述传输方式指示信息用于指示终端采用非接入层NAS信令消息传输业务数据；
    处理器，用于在根据所述通信接口接收到的所述请求消息确定所述终端通过非接入层NAS信令消息传输所述业务数据时，则根据所述终端的签约信息，确定所述终端的第二业务授权信息，所述第二业务授权信息包括用于指示允许所述终端传输业务数据所采用的业务类型和/或优先级的信息；
    所述通信接口，还用于将所述第二业务授权信息发送给所述终端。
  32. 如权利要求31所述的移动管理实体，其特征在于，所述第二业务授权信息还包括第一配额信息，所述第一配额信息用于指示在特定时间内允许发送所述业务类型的业务数据的数量。
  33. 如权利要求31所述的移动管理实体，其特征在于，所述业务授权信息还包括第二配额信息，所述第二配额信息用于指示在特定时间内允许发送的所述优先级的业务数据的数量。
  34. 一种终端，其特征在于，包括：
    发射器，用于发送请求消息给移动管理实体，所述请求消息包含传输方 式指示信息，所述传输方式指示信息用于指示终端采用非接入层NAS信令消息传输业务数据；
    接收器，用于接收所述移动管理实体发送的第二业务授权信息，所述第二业务授权信息包括用于指示允许所述终端传输业务数据所采用的业务类型和/或优先级的信息；
    处理器，用于根据所述接收器接收到的所述第二业务授权信息，确定所述业务数据的信息，所述业务数据的信息包括所述业务数据的业务类型和所述业务数据的优先级中的至少一种；
    所述发射器，还用于将所述处理器确定的所述业务数据的信息发送给所述接入网设备。
  35. 如权利要求34所述的终端，其特征在于，所述第二业务授权信息还包括第一配额信息，所述第一配额信息用于指示在特定时间内被允许发送所述业务类型的业务数据的数量。
  36. 如权利要求34所述的终端，其特征在于，所述第二业务授权信息还包括第二配额信息，所述配额信息用于指示在特定时间内允许发送所述优先级的业务数据的数量。
PCT/CN2016/092521 2016-07-30 2016-07-30 一种业务数据传输方法及设备 WO2018023220A1 (zh)

Priority Applications (5)

Application Number Priority Date Filing Date Title
CN201680087317.0A CN109417729B (zh) 2016-07-30 2016-07-30 一种业务数据传输方法及设备
PCT/CN2016/092521 WO2018023220A1 (zh) 2016-07-30 2016-07-30 一种业务数据传输方法及设备
EP16910818.0A EP3484203B1 (en) 2016-07-30 2016-07-30 Service data transmitting method and equipment
US16/261,026 US10932133B2 (en) 2016-07-30 2019-01-29 Communication of service data based on service authorization information
US17/161,274 US20210153020A1 (en) 2016-07-30 2021-01-28 Service data transmission method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/092521 WO2018023220A1 (zh) 2016-07-30 2016-07-30 一种业务数据传输方法及设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/261,026 Continuation US10932133B2 (en) 2016-07-30 2019-01-29 Communication of service data based on service authorization information

Publications (1)

Publication Number Publication Date
WO2018023220A1 true WO2018023220A1 (zh) 2018-02-08

Family

ID=61072315

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/092521 WO2018023220A1 (zh) 2016-07-30 2016-07-30 一种业务数据传输方法及设备

Country Status (4)

Country Link
US (2) US10932133B2 (zh)
EP (1) EP3484203B1 (zh)
CN (1) CN109417729B (zh)
WO (1) WO2018023220A1 (zh)

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108990112B (zh) * 2017-05-31 2021-01-15 华为技术有限公司 通信网络中的任务处理方法和通信装置
CN112449378A (zh) * 2019-09-05 2021-03-05 华为技术有限公司 一种通信方法及装置
CN110941656A (zh) * 2019-09-23 2020-03-31 新奥数能科技有限公司 基于泛能cim的物联网数据接入方法及装置
CN113132970B (zh) * 2019-12-31 2022-11-29 大唐移动通信设备有限公司 组合业务优先级通知方法及设备
CN111372301A (zh) * 2020-03-17 2020-07-03 杭州凯立通信有限公司 一种移动通信终端及移动通信终端通信技术选择方法
CN111385773A (zh) * 2020-03-24 2020-07-07 武汉科技大学 一种基于nb-iot的智能水表控制电路
CN111757316B (zh) * 2020-06-23 2022-08-19 中国联合网络通信集团有限公司 一种业务连接方法及装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102271367A (zh) * 2011-08-30 2011-12-07 电信科学技术研究院 一种小数据的传输方法和设备
CN102457825A (zh) * 2010-10-15 2012-05-16 电信科学技术研究院 一种数据的传输方法和设备
CN103391532A (zh) * 2012-05-11 2013-11-13 中兴通讯股份有限公司 小量数据上下行传输方法、及相应终端和移动性管理单元
CN103813300A (zh) * 2012-11-14 2014-05-21 华为终端有限公司 数据传输方法、设备及系统
WO2014156230A1 (en) * 2013-03-28 2014-10-02 Nec Corporation Apparatus and methods for small data transmission

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8514756B1 (en) * 2010-10-15 2013-08-20 Juniper Networks, Inc. Collectively addressing wireless devices
CN102790948B (zh) * 2011-05-17 2017-04-05 中兴通讯股份有限公司 一种指示mbms业务中断的方法、装置及用户设备
WO2013053133A1 (zh) * 2011-10-14 2013-04-18 华为技术有限公司 业务数据传输处理方法、设备以及通信系统
US9094828B2 (en) * 2012-02-29 2015-07-28 Alcatel Lucent Machine type communications (MTC) in networks using non access stratum (NAS) signaling
WO2013132289A1 (en) * 2012-03-06 2013-09-12 Nokia Corporation Re-selection optimization for packet and circuit switched connections
US9912597B2 (en) * 2012-03-08 2018-03-06 Samsung Electronics Co., Ltd. Method and apparatus for controlling traffic of radio access network in a wireless communication system
EP2824986B1 (en) * 2013-07-11 2023-03-22 Fujitsu Limited Buffer status reporting in small cell networks
KR102151031B1 (ko) * 2014-06-30 2020-09-02 삼성전자주식회사 저전력 단말의 통신 효과를 높이는 방법 및 장치
EP3200534A4 (en) * 2014-09-25 2018-05-30 LG Electronics Inc. Method and device whereby device-to-device terminal transmits signals in order of priority in wireless communication system
US10694383B2 (en) * 2015-03-23 2020-06-23 Lg Electronics Inc. Method and device for transmitting or receiving data by terminal in wireless communication system
WO2017017931A1 (ja) * 2015-07-24 2017-02-02 日本電気株式会社 移動通信システム、ｍｍｅ、端末、及び通信方法

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102457825A (zh) * 2010-10-15 2012-05-16 电信科学技术研究院 一种数据的传输方法和设备
CN102271367A (zh) * 2011-08-30 2011-12-07 电信科学技术研究院 一种小数据的传输方法和设备
CN103391532A (zh) * 2012-05-11 2013-11-13 中兴通讯股份有限公司 小量数据上下行传输方法、及相应终端和移动性管理单元
CN103813300A (zh) * 2012-11-14 2014-05-21 华为终端有限公司 数据传输方法、设备及系统
WO2014156230A1 (en) * 2013-03-28 2014-10-02 Nec Corporation Apparatus and methods for small data transmission

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3484203A4 *

Also Published As

Publication number Publication date
EP3484203A1 (en) 2019-05-15
US10932133B2 (en) 2021-02-23
EP3484203B1 (en) 2021-09-08
US20210153020A1 (en) 2021-05-20
CN109417729A (zh) 2019-03-01
EP3484203A4 (en) 2019-07-10
CN109417729B (zh) 2022-05-13
US20190159033A1 (en) 2019-05-23

Similar Documents

Publication Publication Date Title
WO2018023220A1 (zh) 一种业务数据传输方法及设备
EP3494723B1 (en) Methods and apparatus for indication of data traffic carried over unlicensed spectrum
US20150288828A1 (en) Method and apparatus for processing charging in wireless communication system and method and apparatus for providing policy service using the same
WO2014000260A1 (zh) 处理QoS的方法、应用服务器、QoS控制网元和移动网络
JP7478267B2 (ja) 課金方法、装置、及びシステム
EP3614625A1 (en) Convergent charging method and device
WO2022001761A1 (zh) 通信方法及装置
RU2656696C1 (ru) Сетевое устройство и способ выделения имени точки доступа
WO2019029581A1 (zh) 一种业务质量流的控制方法及相关设备
CN104969586A (zh) 小数据包的传输方法、基站和用户设备
CN103428731A (zh) 路由优化方法及系统、服务网关
CN111131506B (zh) 报文处理方法及装置
WO2012025031A1 (zh) 基于本地接入的承载建立方法及系统
CN112073925A (zh) 处理数据包的方法及装置
US20190191035A1 (en) Methods and nodes for enabling management of traffic steering policy
WO2015085493A1 (zh) 上行业务数据流的传输装置、方法及系统
WO2021139378A1 (zh) 通信方法和通信装置
WO2018120246A1 (zh) 一种数据传输方法及相关网元
WO2014026326A1 (zh) 控制数据服务质量的方法和装置
WO2016041365A1 (zh) 数据传输的方法和设备
KR101954397B1 (ko) Ｌｔｅ 이동통신 시스템에서 패킷 차단 방법 및 패킷 차단 시스템
KR102271290B1 (ko) 단말 간 통신 시 과금 정보 생성 및 획득 방법
WO2024125232A1 (zh) 一种业务流调度方法及装置
WO2018035687A1 (zh) 一种生成计费数据记录cdr的方法、设备和系统
WO2018040073A1 (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: 16910818

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2016910818

Country of ref document: EP

Effective date: 20190207