Service data transmission method and device

Abstract

A service data transmission method and a device are disclosed, to resolve a problem in the prior art that a network side cannot provide targeted services for different types of NB-IoT services. The method includes: determining, by an access network device, first information of service data to be sent by a terminal, where the first information includes at least one of a service type and a priority; then receiving, by the access network device, the service data sent by the terminal by using a NAS signaling message; and sending, by the access network device, the service data and the first information to a gateway, so that the gateway charges the service data based on the first information after receiving the service data and the first information.

What is claimed is: 
     
         1 . A service data transmission method, comprising:
 receiving, by a terminal, service authorization information from a mobility management entity, wherein the service authorization information comprises information indicating a service type that is allowed to be used by the terminal for transmitting service data, wherein the service authorization information further comprises first quota information, wherein the first quota information indicates a volume of service data that is of the service type and that is allowed to be sent within a particular time, and wherein the service type comprises at least one of the following: an exception report service type, a periodic report service type, a network command service type, or a software upgrading/reconfiguration service type; and   sending, by the terminal based on the service authorization information, information about the service data to an access network device, wherein the information about the service data comprises the service type of the service data.   
     
     
         2 . The method according to  claim 1 , wherein the information about the service data is carried by a radio resource control (RRC) connection setup request message. 
     
     
         3 . The method according to  claim 2 , wherein the RRC connection setup request message comprises an RRC connection setup cause value, and the RRC connection setup cause value is the information about the service data. 
     
     
         4 . The method according to  claim 1 , wherein the information about the service data facilitates the access network device allocating a transmission resource for the service type of the service data. 
     
     
         5 . The method according to  claim 4 , wherein the method further comprises:
 sending, by the terminal, the service data to the access network device via non-access stratum (NAS) signaling based on the transmission resource.   
     
     
         6 . The method according to  claim 5 , wherein the method further comprises:
 sending, by the terminal to the mobility management entity, transmission mode indication information indicating that the terminal transmits service data via a NAS signaling message.   
     
     
         7 . The method according to  claim 6 , wherein the transmission mode indication information is carried by an attach request message. 
     
     
         8 . The method according to  claim 1 , wherein the service type is the exception report service type, and the method further comprises:
 determining, by the terminal, that a volume of sent service data of the exception report service type has not reached the volume indicated in the first quota information; and   based on determining that the volume of sent service data of the exception report service type has not reached the volume indicated in the first quota information, sending, by the terminal, additional service data of the exception report service type.   
     
     
         9 . A terminal, comprising:
 a memory storing processor-executable instructions; and   a processor in communication with the memory;   wherein the processor-executable instructions, when executed by the processor, facilitate performance of the following by the terminal:   receiving service authorization information from a mobility management entity, wherein the service authorization information comprises information indicating a service type that is allowed to be used by the terminal for transmitting service data, wherein the service authorization information further comprises first quota information, wherein the first quota information indicates a volume of service data that is of the service type and that is allowed to be sent within a particular time, and wherein the service type comprises at least one of the following: an exception report service type, a periodic report service type, a network command service type, or a software upgrading/reconfiguration service type; and   sending, based on the service authorization information, information about the service data to an access network device, wherein the information about the service data comprises the service type of the service data.   
     
     
         10 . The terminal according to  claim 9 , wherein the information about the service data is carried by a radio resource control (RRC) connection setup request message. 
     
     
         11 . The terminal according to  claim 10 , wherein the RRC connection setup request message comprises an RRC connection setup cause value, and the RRC connection setup cause value is the information about the service data. 
     
     
         12 . The terminal according to  claim 9 , wherein the processor-executable instructions, when executed by the processor, further facilitate performance of the following by the terminal:
 determining that a volume of sent service data of the exception report service type has not reached the volume indicated in the first quota information; and   based on determining that the volume of sent service data of the exception report service type has not reached the volume indicated in the first quota information, sending additional service data of the exception report service type.   
     
     
         13 . The terminal according to  claim 9 , wherein the information about the service data facilitates the access network device allocating a transmission resource for the service type of the service data. 
     
     
         14 . The terminal according to  claim 13 , wherein the processor-executable instructions, when executed by the processor, further facilitate performance of the following by the terminal:
 sending the service data to the access network device via non-access stratum (NAS) signaling based on the transmission resource.   
     
     
         15 . A non-transitory computer readable storage medium comprising processor-executable instructions, wherein the processor-executable instructions, when executed, facilitate:
 receiving service authorization information from a mobility management entity, wherein the service authorization information comprises information indicating a service type that is allowed to be used by the terminal for transmitting the service data, wherein the service authorization information further comprises first quota information, wherein the first quota information indicates a volume of service data that is of the service type and that is allowed to be sent within a particular time, and wherein the service type comprises at least one of the following: an exception report service type, a periodic report service type, a network command service type, or a software upgrading/reconfiguration service type; and   sending, based on the second service authorization information, information about the service data to an access network device, wherein the information about the service data comprises the service type of the service data.   
     
     
         16 . The non-transitory computer readable storage medium according to  claim 15 , wherein the information about the service data is carried by a radio resource control (RRC) connection setup request message. 
     
     
         17 . The non-transitory computer readable storage medium according to  claim 16 , wherein the RRC connection setup request message comprises an RRC connection setup cause value, and the RRC connection setup cause value is the information about the service data. 
     
     
         18 . The non-transitory computer readable storage medium according to  claim 15 , wherein the information about the service data facilitates the access network device allocating a transmission resource for the service type of the service data. 
     
     
         19 . The non-transitory computer readable storage medium according to  claim 15 , wherein the processor-executable instructions, when executed, further facilitate:
 sending the service data to the access network device via non-access stratum (NAS) signaling based on the transmission resource.   
     
     
         20 . The non-transitory computer readable storage medium according to  claim 15 , wherein the processor-executable instructions, when executed, further facilitate:
 determining that a volume of sent service data of the exception report service type has not reached the volume indicated in the first quota information; and   based on determining that the volume of sent service data of the exception report service type has not reached the volume indicated in the first quota information, sending additional service data of the exception report service type.