WO2014047920A1 - 数据传输方法、设备及系统 - Google Patents

数据传输方法、设备及系统 Download PDF

Info

Publication number
WO2014047920A1
WO2014047920A1 PCT/CN2012/082430 CN2012082430W WO2014047920A1 WO 2014047920 A1 WO2014047920 A1 WO 2014047920A1 CN 2012082430 W CN2012082430 W CN 2012082430W WO 2014047920 A1 WO2014047920 A1 WO 2014047920A1
Authority
WO
WIPO (PCT)
Prior art keywords
mme
terminal device
message
type
cscf
Prior art date
Application number
PCT/CN2012/082430
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 CN201280001720.9A priority Critical patent/CN103891321B/zh
Priority to EP12885203.5A priority patent/EP2884780B1/en
Priority to PCT/CN2012/082430 priority patent/WO2014047920A1/zh
Publication of WO2014047920A1 publication Critical patent/WO2014047920A1/zh
Priority to US14/671,724 priority patent/US9549424B2/en

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/20Services signaling; Auxiliary data signalling, i.e. transmitting data via a non-traffic channel
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066Session management
    • H04L65/1101Session protocols
    • H04L65/1104Session initiation protocol [SIP]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W68/00User notification, e.g. alerting and paging, for incoming communication, change of service or the like
    • H04W68/005Transmission of information for alerting of incoming communication
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/20Control channels or signalling for resource management
    • H04W72/21Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/10Connection setup
    • H04W76/11Allocation or use of connection identifiers
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W88/00Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/18Service support devices; Network management devices
    • H04W88/182Network node acting on behalf of an other network entity, e.g. proxy

Definitions

  • the present invention relates to communications technologies, and in particular, to a data transmission method, device, and system. Background technique
  • Machine Type Communication refers to network communication between one or more network elements or devices without human intervention. It can also be called Machine to Machine (Machine to Machine, Referred to as M2M) communication. MTC and some other communication similar to MTC have the characteristics of small interaction traffic and mutual burst. Therefore, data transmission in MTC and other communication processes similar to MTC is often called Small Data Transmission (English). Data traffic (Low Data Usage) is transmitted. Correspondingly, compared with human to human (H2H) terminals, MTC terminals and terminals like MTC terminals are often referred to as small data transmission terminals or low data. Traffic terminal.
  • MTC Machine to Machine
  • the MTC architecture mainly includes an MTC-Interworking Function (MTC-IWF) network element and a Service Capability Server (SCS).
  • MTC-IWF mainly implements SCS authentication, external identifier mapping, and querying the home subscriber server (Home Subscriber Server, HSS for short) to obtain service node information in the mobile communication network;
  • SCS provides MTC application capabilities, such as M2M terminal triggering, etc.
  • Service capability, and the MTC application is provided by an application server (Application Server, abbreviated as AS) outside the MTC architecture.
  • AS Application Server
  • a network element in a mobile communication network such as a Packet Data Network Gateway (PGW), and an Internet Protocol (Internet Protocol) is assigned to each small data transmission terminal.
  • IP Packet Data Network Gateway
  • IP Internet Protocol
  • RAB Radio Access Bear
  • a first aspect of the embodiments of the present invention provides a data transmission method, including:
  • the terminal device determines whether the data amount of the uplink data to be sent is less than a preset data amount threshold; when the data amount of the uplink data is less than the preset data amount threshold, the terminal device sends a radio resource control RRC connection request message to the base station.
  • the RRC connection request message includes indication information indicating that the base station only establishes a signaling connection for the terminal device;
  • the terminal device carries the uplink data in an RRC connection complete message and sends the data to the base station, so that the base station passes the uplink data between the base station and the mobility management entity MME according to the indication information.
  • the first type of first signaling message is sent to the MME to enable the MME to pass the second type between the MME and the proxy call session control function P-CSCF in a first possible implementation on the one hand
  • the terminal device determines whether the amount of data of the uplink data to be sent is less than a preset data volume threshold, and includes:
  • the terminal device sends an attach request message to the MME, so that the MME sends a first session initial to the application server by using a second type of second signaling message between the MME and the P-CSCF.
  • a SIP registration request message the attachment request message includes an identifier of the terminal device
  • the first SIP registration request message includes an identifier of the terminal device and a SIP identifier corresponding to the terminal device;
  • an attach accept message sent by the MME where the attach accept message is that the MME receives the application by using a third type of third signaling message between the MME and the P-CSCF
  • the first SIP registration completion message is returned by the application server after receiving the SIP identifier corresponding to the terminal device;
  • the determining, by the terminal device, whether the data volume of the uplink data to be sent is less than a preset data volume threshold includes:
  • the determining, by the terminal device, whether the data volume of the uplink data to be sent is less than a preset data volume threshold includes:
  • the terminal device sends an attach request message to the MME, where the attach request message includes an identifier of the terminal device;
  • the data transmission method further includes:
  • the terminal device sends a service request message to the MME according to the paging message, where the service request message is used to indicate that the MME only establishes a signaling connection for the terminal device;
  • the terminal device receives a fourth signaling message of the first type that is sent by the MME according to the service request message, where the fourth signaling message of the first type includes the downlink data.
  • a second aspect of the embodiments of the present invention provides a data transmission method, including: Receiving, by the base station, a radio resource control RRC connection request message sent by the terminal device, where the RRC connection request message is generated when the terminal device determines that the data volume of the uplink data to be sent is less than a preset data quantity threshold, the RRC connection request message Including indicating that the base station only establishes a signaling connection for the terminal device;
  • the third aspect of the second embodiment of the present invention between the MME and the proxy call session control function P-CSCF provides a data transmission method, including:
  • the mobility management entity MME receives the first type of first signaling message sent by the base station, where the first type of the first signaling message is after the base station receives the radio resource control RRC connection complete message sent by the terminal device, According to the indication information in the RRC connection request message sent by the terminal device, the RRC connection complete message includes uplink data sent by the terminal device to the application server, where the first type of first signaling message includes The uplink data, where the indication information is used to indicate that the base station only establishes a signaling connection for the terminal device;
  • the MME sends the uplink data to the application server by using a first type of first signaling message between the MME and the proxy call session control function P-CSCF.
  • the method before the mobility management entity MME receives the first signaling message of the first type sent by the base station, the method includes:
  • the MME obtains a session initial protocol SIP identifier corresponding to the terminal device according to the identifier of the terminal device, and generates a first SIP registration request message, where the first SIP registration request message includes the identifier and location of the terminal device. Said SIP identifier corresponding to the terminal device;
  • the acquiring, by the MME, the SIP identifier corresponding to the terminal device according to the identifier of the terminal device includes:
  • the MME generates a SIP identifier corresponding to the terminal device according to the identifier of the terminal device.
  • the method before the mobility management entity MME receives the first signaling message of the first type sent by the base station, the method includes:
  • the MME allocates an IP address to the terminal device
  • the MME Receiving, by the MME, the first signaling message of the first type that is sent by the terminal device according to the IP address, where the second signaling message of the first type includes a first SIP registration request message, the first SIP registration
  • the request message includes an identifier of the terminal device and a SIP identifier corresponding to the terminal device;
  • the MME receives, by the MME, a third type of third signaling message between the MME and the P-CSCF, the first SIP registration completion message returned by the application server after receiving the SIP identifier corresponding to the terminal device ;
  • the MME sends a first type of third signaling message to the terminal device, where the first type of third signaling message includes the first SIP registration complete message;
  • the method before the mobility management entity MME receives the first signaling message of the first type sent by the base station, the method includes:
  • the MME Sending, by the MME, a second SIP registration request message to the P-CSCF by using a second type of second signaling message between the MME and the P-CSCF, so that the P-CSCF
  • the second SIP registration request message is sent to the application server, the second type of second signaling message includes the second SIP registration request message, and the second SIP registration request message includes the identifier and location of the MME. Describe the SIP identifier corresponding to the MME;
  • the MME by using the second type of third information between the MME and the P-CSCF After the message is received, the second SIP registration completion message returned by the application server after receiving the SIP identifier corresponding to the MME includes:
  • the data transmission method further includes:
  • the MME receives downlink data sent by the application server to the terminal device by using a fourth type of fourth signaling message between the MME and the P-CSCF;
  • the fourth type of signaling message includes the downlink data.
  • the MME is configured to perform a second between the MME and the proxy call session control function P-CSCF
  • the first signaling message of the type, the sending the uplink data to the application server includes:
  • the MME sends a third type of first signaling message to the MSC server, where the third type of first signaling message includes the uplink data, so that the MSC server encapsulates the uplink data in the first
  • the first type of the first signaling message is sent to the P-CSCF to send the uplink data to the application server.
  • the MME by using the second type of fourth information between the MME and the P-CSCF The message, the receiving the downlink data sent by the application server to the terminal device, includes:
  • the third type of second signaling message generated by the signaling message includes the downlink data.
  • a fourth aspect of the embodiments of the present invention provides a data transmission method, including:
  • the proxy call session control function P-CSCF receives the uplink data sent by the terminal device to the application server by using the first type of the first signaling message between the P-CSCF and the mobility management entity MME;
  • the first signaling message is generated by the MME according to the uplink data in the first signaling message of the first type, after receiving the first signaling message of the first type sent by the eNB, the second
  • the first signaling message of the type includes the uplink data, where the data volume of the uplink data is less than a preset data volume threshold;
  • the P-CSCF sends the uplink data to the S-CSCF, so that the S-CSCF sends the uplink data to the application server.
  • the proxy call session control function P-CSCF receives the first type of first signaling message between the P-CSCF and the mobility management entity MME.
  • the uplink data sent by the terminal device to the application server includes:
  • the P-CSCF Passing, by the P-CSCF, a second type of second signaling between the P-CSCF and the MME Receiving, by the message, the first SIP registration request message sent by the MME, where the first SIP registration request message includes an identifier of the terminal device and a SIP identifier corresponding to the terminal device;
  • the P-CSCF sends the first SIP registration complete message to the MME by using a second type of third signaling message between the P-CSCF and the MME.
  • the proxy call session control function P-CSCF receives the first type of first signaling message between the P-CSCF and the mobility management entity MME.
  • the uplink data sent by the terminal device to the application server includes:
  • the P-CSCF receives a second SIP registration request message sent by the MME by using a second type of second signaling message between the P-CSCF and the MME, where the second SIP registration request message includes The identifier of the MME and the SIP identifier corresponding to the MME;
  • the P-CSCF sends the second SIP registration complete message to the MME by using a second type of third signaling message between the P-CSCF and the MME.
  • the data transmission method further includes:
  • the S-CSCF Receiving, by the S-CSCF, the downlink data sent by the application server to the terminal device and the address information of the MME, where the address information of the MME is corresponding to the S-CSCF according to the terminal device
  • the SIP identifier is obtained by the home storage server HSS, and the HSS stores a mapping relationship between the identifier of the terminal device and the SIP identifier corresponding to the terminal device, and the identifier of the terminal device and the address of the MME. Mapping relationship between information;
  • the P-CSCF sends the downlink data to the MME by using a fourth type of fourth signaling message between the P-CSCF and the MME according to the address information of the MME.
  • the proxy call session control function P-CSCF by using the P-CSCF and the mobility
  • the first type of the first signaling message is sent between the MME and the MME, and the uplink data sent by the receiving terminal to the application server includes:
  • the P-CSCF receives the second signaling message sent by the MSC server, where the second signaling message is generated by the MSC server according to the third type of first signaling message sent by the MME,
  • the third type of first signaling message includes the uplink data.
  • the P-CSCF by using the P-CSCF and the MME, according to address information of the MME
  • the sending of the downlink data to the MME includes:
  • a second type of signaling message is sent to the MME.
  • a fifth aspect of the embodiments of the present invention provides a terminal device, including:
  • a determining module configured to determine whether the data volume of the uplink data to be sent is less than a preset data volume threshold;
  • the first sending module configured to determine, in the determining module, that the data volume of the uplink data is smaller than the preset data volume gate Sending a radio resource control RRC connection request message to the base station, where the RRC connection request message includes indication information indicating that the base station only establishes a signaling connection for the terminal device;
  • a first receiving module configured to: after the first sending module sends the RRC connection request message, receive an RRC connection setup message sent by the base station;
  • the first sending module is further configured to: after the first receiving module receives the RRC connection setup message, send the uplink data to an RRC connection complete message, and send the uplink data to the base station, so that the base station is configured according to the Sending, by the indication information, the uplink data to the MME by using a first type of first signaling message between the base station and the mobility management entity MME, so that the MME calls through the MME and the proxy
  • the first sending module is further configured to determine, in the determining module, that the uplink data is to be sent.
  • the first request module includes an identifier of the terminal device, where the first SIP registration request message includes an identifier of the terminal device and a SIP identifier corresponding to the terminal device; After the first sending module sends the attach request message to the MME, receiving an attach accept message sent by the MME, where the attach accept message is the first time between the MME and the P-CSCF by the MME After the third type of the third signaling message is received by the application server, the first SIP registration completion message is that the application server receives the SIP identifier corresponding to the terminal device. Returned after
  • the first sending module is further configured to send, to the MME, before the determining module determines whether the data volume of the uplink data to be sent is less than a preset data volume threshold
  • An attach request message where the attach request message includes an identifier of the terminal device, and configured to: after the first receiving module receives an attach accept message sent by the MME, according to the MME in the attach accept message Sending, by the terminal device, an IP address, a first SIP registration request message to the MME by using a first signaling message of the first type between the terminal device and the MME, so that the MME passes the Sending, by the MME and the P-CSCF, a second signaling message of the second type, the first SIP registration request message to the application server, where the first SIP registration request message includes the terminal device Identifying a SIP identifier corresponding to the terminal device;
  • the first receiving module is further configured to: after the first sending module sends the attach request message to the MME, receive the attach accept message sent by the MME, where the attach accept message includes the MME The IP address assigned by the terminal device; and after the first sending module sends the first SIP registration request message to the MME, by using the first type between the terminal device and the MME Receiving, by the third signaling message, a first SIP registration complete message returned by the MME, where the first SIP registration complete message is returned by the application server after receiving the SIP identifier corresponding to the terminal device, where the MME is Receiving, by the second type of third signaling message between the MME and the P-CSCF, the first SIP registration complete message; There is only a signaling connection between the terminal device and the MME.
  • the first sending module is further configured to send, to the MME, before the determining module determines whether the data volume of the uplink data to be sent is less than a preset data volume threshold
  • An attach request message where the attach request message includes an identifier of the terminal device
  • the first receiving module is further configured to: after the first sending module sends the attach request message to the MME, send the MME to send Attachment acceptance message;
  • the first receiving module is further configured to receive a paging message sent by the MME, and receive a fourth type of fourth message sent by the MME according to the service request message sent by the first sending module.
  • a message, the paging message is that the MME receives the downlink data sent by the application server to the terminal device by using a fourth type of fourth signaling message between the MME and the P-CSCF.
  • the generated fourth signaling message of the first type includes the downlink data;
  • the first sending module is further configured to: after the first receiving module receives the paging message, send a service request message to the MME, where the service request message is used to indicate that the MME is only the terminal
  • the device establishes a signaling connection.
  • a sixth aspect of the embodiments of the present invention provides a terminal device, including:
  • a processor configured to determine whether a data quantity of the uplink data to be sent is less than a preset data quantity threshold, and a transmitter, configured to: when the processor determines that the data quantity of the uplink data is less than the preset data quantity threshold, Sending, to the base station, a radio resource control RRC connection request message, where the RRC connection request message includes indication information indicating that the base station only establishes a signaling connection for the terminal device, and a receiver, configured to send the RRC at the transmitter After the connection request message, receiving an RRC connection setup message sent by the base station;
  • the transmitter is further configured to: after the receiver receives the RRC connection setup message, send the uplink data to an RRC connection complete message, and send the uplink data to the base station, so that the base station is configured according to the indication information. Transmitting, by the MME, the first type of first signaling message between the base station and the mobility management entity MME to the MME, so that the MME passes the MME and proxy call session control function P. a second type of first signaling message between the CSCFs to be said The row data is sent to the application server corresponding to the uplink data.
  • a seventh aspect of the embodiments of the present invention provides a base station, including:
  • a second receiving module configured to receive a radio resource control RRC connection request message sent by the terminal device, and receive an RRC connection complete message sent by the terminal device after the second sending module sends an RRC connection setup message to the terminal device,
  • the RRC connection request message is generated when the terminal device determines that the data volume of the uplink data to be sent is less than a preset data volume threshold, where the RRC connection request message includes the base station only to establish signaling for the terminal device.
  • the second sending module is configured to: after the second receiving module receives the RRC connection request message, send the RRC connection setup message to the terminal device, and receive the location in the second receiving module After the RRC connection complete message, the uplink data is sent to the MME by using a first type of first signaling message between the base station and the mobility management entity MME according to the indication information, so that the The MME sends the uplink data to the application server corresponding to the uplink data by using a first type of first signaling message between the MME and the proxy call session control function P-CSCF.
  • An eighth aspect of the embodiments of the present invention provides a base station, including: a receiver and a transmitter, where the receiver is configured to receive a radio resource control RRC connection request message sent by the terminal device, and send the transmitter to the terminal
  • the device receives the RRC connection complete message sent by the terminal device, where the RRC connection request message is generated when the terminal device determines that the data volume of the uplink data to be sent is less than the preset data volume threshold.
  • the RRC connection request message includes indication information indicating that the base station only establishes a signaling connection for the terminal device, and the RRC connection complete message includes the uplink data;
  • the transmitter is configured to: after the receiver receives the RRC connection request message, send the RRC connection setup message to the terminal device, and after the receiver receives the RRC connection complete message, And sending, according to the indication information, the uplink data to the MME by using a first type of first signaling message between the base station and the mobility management entity MME, so that the MME passes the MME and
  • the ninth aspect of the second embodiment of the present invention is the mobility management entity MME, which includes: a third receiving module, configured to receive the first type of the first type sent by the base station a signaling message, the first A type of first signaling message is that the base station receives the radio resource control sent by the terminal device.
  • the RRC connection complete message includes uplink data sent by the terminal device to the application server, where the first type is The signaling message includes the uplink data, where the indication information is used to indicate that the base station only establishes a signaling connection for the terminal device;
  • a third sending module configured to send the uplink data to the application server by using a second type of first signaling message between the MME and the proxy call session control function P-CSCF.
  • the third receiving module is further configured to: before receiving the first signaling message of the first type, receive an attach request message sent by the terminal device, and After the third sending module sends the first SIP registration request message to the application server, receiving, by using the third type of third signaling message between the MME and the P-CSCF, the application server is a first SIP registration complete message returned after receiving the SIP identifier corresponding to the terminal device, where the attach request message includes an identifier of the terminal device;
  • the MME further includes:
  • An acquiring module configured to acquire, according to the identifier of the terminal device, a session initial protocol SIP identifier corresponding to the terminal device, and generate the first SIP registration request message, where the first SIP registration request message includes the terminal device The identifier and the SIP identifier corresponding to the terminal device;
  • the third sending module is further configured to send the first SIP registration request message to the application server by using a second type of second signaling message between the MME and the P-CSCF, and in the After receiving the first SIP registration complete message, the third receiving module sends an attach accept message to the terminal device, where the attach accept message includes the first SIP registration complete message, where the terminal device and the There is only a signaling connection between the MMEs.
  • the acquiring module is specifically configured to send a location update request message to the location home server HSS, where the location update request message includes an identifier of the terminal device, and receives the terminal device returned by the HSS according to the identifier of the terminal device. a mapping relationship between the identifier and the SIP identifier corresponding to the terminal device; or
  • the acquiring module is specifically configured to generate, according to the identifier of the terminal device, the terminal device pair The SIP ID should be.
  • the third receiving module is further configured to: before receiving the first signaling message of the first type, receive an attach request message sent by the terminal device, and After the third sending module sends an attach accept message to the terminal device, receiving the second signaling message, and after the third sending module sends the first SIP registration request message to the application server, receiving the a first SIP registration complete message returned by the application server after receiving the SIP identifier corresponding to the terminal device;
  • the attach request message includes an identifier of the terminal device, where the second type of the first signaling message includes a first SIP registration request message, where the first SIP registration request message includes an identifier of the terminal device and a SIP identifier corresponding to the terminal device;
  • the MME further includes: an allocation module, configured to allocate the terminal device
  • the third sending module is further configured to: after the third receiving module receives the attach request message, to the terminal The attach accept message is sent, the attach accept message includes the IP address, and after the third receiving module receives the second signaling message of the
  • the third sending module is further configured to: before the third receiving module receives the first signaling message of the first type, by using the MME and the Transmitting a second type of second signaling message between the P-CSCFs, and sending a second SIP registration request message to the P-CSCF, so that the P-CSCF sends the second SIP registration request message to the The application server, the second type of the second signaling message includes the second SIP registration request message, and the second SIP registration request message includes an identifier of the MME and a SIP identifier corresponding to the MME;
  • the third receiving module is further configured to: after the third sending module sends the second SIP registration request message, by using a third type of third signaling message between the MME and the P-CSCF, Receiving a second SIP registration completion message returned by the application server after receiving the SIP identifier corresponding to the MME.
  • the third receiving module is further configured to: after receiving the second SIP registration complete message, receive An attach request message sent by the terminal device, where the attach request message includes an identifier of the terminal device;
  • the third sending module is further configured to: after the third receiving module receives the attach request message, send an attach accept message to the terminal device;
  • the third receiving module is further configured to pass between the MME and the P-CSCF The fourth type of the fourth signaling message, receiving the downlink data sent by the application server to the terminal device, and receiving the terminal device after the third sending module sends the paging message to the terminal device Service request message sent;
  • the third sending module is further configured to: after the third receiving module receives the downlink data, send the paging message to the terminal device, and receive the service request at the third receiving module. After the message, the fourth signaling message of the first type is sent to the terminal device, where the fourth signaling message of the first type includes the downlink data.
  • the third sending module is configured to use the MME and the proxy call session control function P-CSCF
  • the first type of the first signaling message is sent, and the sending the uplink data to the application server includes:
  • the third sending module is specifically configured to send a third type of first signaling message to the MSC server, where the third type of first signaling message includes the uplink data, so that the MSC server sends the uplink Data encapsulation is sent to the P-CSCF in the first type of first signaling message to send the uplink data to the application server.
  • the third receiving module is configured to use the first between the MME and the P-CSCF And receiving, by the second type of the fourth signaling message, the downlink data that is sent by the application server to the terminal device, where
  • the third receiving module is specifically configured to receive a third type of second signaling message sent by the MSC server, where the second type of the second signaling message is sent by the MSC server according to the P-CSCF
  • the second signaling message of the third type is generated by the fourth type of the fourth signaling message.
  • a tenth aspect of the embodiments of the present invention provides a mobility management entity, including:
  • the RRC connection complete message includes uplink data sent by the terminal device to the application server, where the first type of first signaling message includes The uplink data, where the indication information is used to indicate that the base station only establishes a signaling connection for the terminal device;
  • a transmitter configured to send the uplink data to the application server by using a second type of first signaling message between the MME and the proxy call session control function P-CSCF.
  • the eleventh embodiment of the present invention provides a proxy call session control function P-CSCF, which includes:
  • a fourth receiving module configured to receive, by using a second type of first signaling message between the P-CSCF and the mobility management entity MME, uplink data that is sent by the terminal device to the application server; a signaling message is generated by the MME according to the uplink data in the first signaling message of the first type, after receiving the first signaling message of the first type sent by the eNB, the second type
  • the first signaling message includes the uplink data, and the data volume of the uplink data is less than a preset data volume threshold;
  • a fourth sending module configured to send the uplink data to the S-CSCF, so that the S-CSCF sends the uplink data to the application server.
  • the fourth receiving module is further configured to: before receiving the uplink data, by using a second type between the P-CSCF and the MME Receiving, by the second sending message, the first SIP registration request message sent by the MME, and after the fourth sending module sends the first SIP registration request message to the application server, receiving the S-CSCF to send Receiving, by the application server, the SIP identifier corresponding to the terminal device a first SIP registration completion message, where the first SIP registration request message includes an identifier of the terminal device and a SIP identifier corresponding to the terminal device;
  • the fourth sending module is further configured to: after the fourth receiving module receives the first SIP registration request message, send the first SIP registration request message to the S-CSCF, so that the S Sending, by the CSCF, the first SIP registration request message to the application server, and after the fourth receiving module receives the first SIP registration complete message, between the P-CSCF and the MME
  • the second type of third signaling message sends the first SIP registration complete message to the MME.
  • the fourth receiving module is further configured to: before receiving the uplink data, by using a second type between the P-CSCF and the MME Receiving, by the second signaling message, a second SIP registration request message sent by the MME, and after the fourth sending module sends the second SIP registration request message to the S-CSCF, receiving the S-CSCF a second SIP registration completion message that is sent by the application server after receiving the SIP identifier corresponding to the MME, where the second SIP registration request message includes an identifier of the MME and a SIP identifier corresponding to the MME;
  • the fourth sending module is further configured to: after the fourth receiving module receives the second SIP registration request message, send the second SIP registration request message to the S-CSCF, so that the S Sending, by the CSCF, the second SIP registration request message to the application server, and after the fourth receiving module receives the second SIP registration complete message, between the P-CSCF and the MME
  • the second type of third signaling message sends the second SIP registration complete message to the MME.
  • the fourth receiving module is further configured to receive the application server that is sent by the S-CSCF The downlink data sent to the terminal device and the address information of the MME, where the address information of the MME is obtained by the S-CSCF querying the home storage server HSS according to the SIP identifier corresponding to the terminal device, where the HSS storage is a mapping relationship between the identifier of the terminal device and the SIP identifier corresponding to the terminal device, and a mapping relationship between the identifier of the terminal device and the address information of the MME;
  • the fourth sending module is further configured to: after the fourth receiving module receives the downlink data and the address information of the MME, according to the address information of the MME, pass the P-CSCF and the Transmitting the downlink data to the MME by using a fourth type of fourth signaling message between the MMEs.
  • the fourth receiving module is configured to send, by using the first signaling message of the second type between the P-CSCF and the mobility management entity MME, the receiving terminal device to send to the application server.
  • the uplink data includes:
  • the fourth receiving module is specifically configured to receive the first signaling message of the second type that is sent by the MSC server, where the first signaling message of the second type is the third that is sent by the MSC server according to the MME. Generated by the first signaling message of the type, the first signaling message of the third type includes the uplink data.
  • the fourth sending module is configured to pass the P- according to the address information of the MME Sending the downlink data to the MME by using the fourth type of the fourth signaling message between the CSCF and the MME includes:
  • the fourth sending module is specifically configured to send the fourth type of fourth signaling message to the MSC server, so that the MSC server sends the downlink data in the fourth type of fourth signaling message.
  • the encapsulation is sent to the MME in a second type of second signaling message.
  • a twelfth aspect of the embodiments of the present invention provides a proxy call session control function, including: a receiver, configured to receive, by using a second type of first signaling message between the P-CSCF and a mobility management entity MME The first type of the first signaling message is sent by the MME to the first type of the first signaling message sent by the base station, according to the first type of the first type And generating, by the uplink data in the signaling message, the first signaling message of the second type includes the uplink data, where a data volume of the uplink data is less than a preset data volume threshold;
  • a transmitter configured to send the uplink data to the S-CSCF, so that the S-CSCF sends the uplink data to the application server.
  • a thirteenth aspect of the present invention provides a data transmission system, including: any terminal device provided by the fifth aspect of the present invention, any base station provided by the seventh aspect of the embodiment of the present invention, and the ninth embodiment of the present invention Any of the mobility management entity MMEs provided by the aspect and any of the proxy call session control functions P-CSCF provided by the eleventh embodiment of the present invention; the P-CSCF and the MME connection.
  • the data transmission method, device and system provided by the embodiment of the present invention perform small data transmission based on a first type of signaling message between the MME and the terminal device and a second type of signaling message between the MME and the P-CSCF. There is no need to specifically establish or restore the user plane RAB of the terminal device and the network air interface side, which saves network resources.
  • BRIEF DESCRIPTION OF THE DRAWINGS In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, a brief description of the drawings used in the embodiments or the prior art description will be briefly described below. The drawings are some embodiments of the present invention, and those skilled in the art can obtain other drawings based on these drawings without any inventive labor.
  • FIG. 1 is a system architecture diagram for implementing small data transmission based on the following embodiments of the present invention
  • FIG. 2 is a flowchart of a data transmission method according to an embodiment of the present invention.
  • FIG. 3 is a flowchart of a data transmission method according to another embodiment of the present invention.
  • FIG. 4 is a flowchart of a data transmission method according to another embodiment of the present invention.
  • FIG. 5 is a schematic diagram of another system architecture for implementing small data transmission based on embodiments of the present invention
  • FIG. 6 is a flowchart of a data transmission method according to another embodiment of the present invention.
  • FIG. 7 is a system architecture diagram of a small data transmission method according to an embodiment of the present invention
  • FIG. 8 is a flowchart of a small data transmission method according to an embodiment of the present invention
  • 9A is a flowchart of a registration method according to an embodiment of the present invention.
  • 9B is a flowchart of a registration method according to another embodiment of the present invention.
  • 9C is a flowchart of a registration method according to another embodiment of the present invention.
  • 9D is a flowchart of a small data transmission method according to another embodiment of the present invention.
  • FIG. 10 is a flowchart of a small data transmission method according to another embodiment of the present invention.
  • FIG. 11 is a schematic structural diagram of a terminal device according to an embodiment of the present invention.
  • FIG. 12 is a schematic structural diagram of a terminal device according to another embodiment of the present disclosure.
  • FIG. 13 is a schematic structural diagram of a base station according to an embodiment of the present invention.
  • FIG. 14 is a schematic structural diagram of a base station according to another embodiment of the present disclosure.
  • FIG. 15 is a schematic structural diagram of an MME according to an embodiment of the present disclosure
  • FIG. 16 is a schematic structural diagram of an MME according to another embodiment of the present disclosure
  • FIG. 17 is a schematic structural diagram of a P-CSCF according to an embodiment of the present invention.
  • FIG. 18 is a schematic structural diagram of a P-CSCF according to another embodiment of the present invention.
  • the technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention.
  • the embodiments are a part of the embodiments of the invention, and not all of the embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.
  • the following embodiments provide a new data transmission method, which uses signaling.
  • the message transmission small data does not need to create a user plane RAB for the transmission of small data, and does not need to reserve corresponding resources for transmitting small data, which not only solves the transmission of small data, but also solves the problem of transmitting small data in the prior art.
  • the small data in various embodiments of the present invention may be small data in the middle of the MTC, or may be small data in other communication systems.
  • the so-called small data refers to data whose data amount is less than the preset data amount threshold.
  • the preset data volume threshold may be set according to different communication systems or requirements. The specific values of the embodiment are not limited.
  • FIG. 1 is a system architecture diagram of implementing small data transmission based on the following embodiments of the present invention.
  • the system in this embodiment includes: a base station, a Mobility Management Entity (MME), a Serving Gateway (SGW for short), a PGW, and a home subscriber server (Home Subscriber). Server, referred to as HSS), Proxy-Call Session Control Function (P-CSCF for short), Serving-Call Session Control Function (S-CSCF for short) and AS, where
  • MME, the PGW, and the SGW are three functional entities in the core network of the wireless evolved network.
  • the P-CSCF and the S-CSCF are core processing components of the IMS network, and are used to control functions such as user registration and session control.
  • the S-CSCF is in the core control position during the session control process of the entire IMS core network, accepts the registration request forwarded by the IMS terminal from the visited network through the P-CSCF, cooperates with the HSS to authenticate the IMS terminal user, and downloads from the HSS.
  • IMS Basic subscription data performing basic session routing functions for the calling end and the called end IMS end user.
  • the architecture further includes: a user equipment (User Equipment, abbreviated as UE) and a public data network (Public Data Network, PDN for short).
  • UE User Equipment
  • PDN Public Data Network
  • the UE in the embodiments of the present invention may be various small data transmission terminals or low data traffic terminals, and may be, for example, an MTC terminal, but is not limited thereto.
  • the UE of the embodiments of the present invention may have large data transmission in addition to the small data transmission.
  • the so-called big data is relative to d, data.
  • the UE is connected to the base station, and the interface between the two is a Uu interface;
  • the base station is connected to the MME, and the interface between the two is an S1-MME interface;
  • the base station is connected to the SGW, and the interface between the two is S-U interface;
  • SGW is connected to PGW, the interface between the two is an S5/S8 interface;
  • the PGW is connected to the PDN, and the interface between the two is an SGi interface;
  • the SGW is connected to the MME, and the interface between the two is SI.
  • MME is connected to HSS, the interface between the two is S6a interface
  • P-CSCF is connected to MME
  • P-CSCF is connected to S-CSCF
  • S-CSCF is connected to HSS, and the interface between the two is Cx interface
  • AS is connected to the S-CSCF.
  • AS is an application server in a small data transmission system, and its connection relationship with the S-CSCF depends on the structure of the small data transmission system. For example, if the small data transmission system is an MTC system, the AS can be directly connected to the S-CSCF, or can be connected to the S-CSCF through the SCS in the MTC system, or can be connected to the S-CSCF through the SCS and the MTC-IWF.
  • the interface between the AS and the S-CSCF or the interface between the SCS and the S-CSCF is called an ISC interface
  • the interface between the SCS and the MTC-IWF is called a Tsp interface.
  • the names of the interfaces mentioned above are not limited thereto, and the embodiment is merely described as an example.
  • the Cx interface can be implemented by using the Diameter protocol, and the Diameter protocol is an upgraded version of the Remote Authentication Dial In User Service (RADIUS) protocol.
  • the main functions of the Cx interface include the S-CSCF and the The interaction between the authentication information and the subscription information between the HSS, and the query of the S-CSCF information assigned by the user; the Tsp interface is mainly used for transmitting control device signaling and other related control plane signaling; the ISC interface can use the Session Initiation protocol (Session Initiation)
  • the protocol referred to as SIP, is implemented.
  • the S-CSCF communicates with the AS through the interface to implement support for small data services.
  • connection or connected includes direct connection or connection, as well as indirect connection or connection via other devices or network elements.
  • the architecture implements an interface between a small data transmission system and an IMS network, and supports transmission of small amounts of data in a small data transmission system through an IMS network element.
  • MME and The P-CSCF is connected instead of being connected to the P-CSCF by the PGW, which provides conditions for small data to be transmitted between the UE and the MME through signaling messages, so that the small data transmission may not need to establish a default user plane RAB.
  • the flow of the data transmission method provided by the embodiment of the present invention will be described below by taking the system architecture shown in FIG. 1 as an example.
  • FIG. 2 is a flowchart of a data transmission method according to an embodiment of the present invention. This embodiment is explained from the perspective of the terminal device. As shown in FIG. 1, the method in this embodiment includes:
  • Step 101 The terminal device determines whether the data volume of the uplink data to be sent is less than a preset data volume threshold. If the determination result is yes, that is, the data volume of the uplink data is less than the preset data volume threshold, step 102 is performed; if the determination result is no Optionally, the terminal device can send the uplink data according to the sending process in the prior art.
  • the data sent by the terminal device to the application server is referred to as uplink data, and correspondingly, the data transmitted by the application server to the terminal device is referred to as downlink data.
  • the terminal device when the terminal device needs to send the uplink data to the application server, it is determined whether the data volume of the uplink data to be sent is small data, and the determining process is specifically determining whether the data volume of the uplink data to be sent is less than a preset data volume threshold. If the judgment result is yes, the uplink data to be sent is small data. If the judgment result is no, the uplink data to be sent is not small data (that is, big data).
  • the terminal device continues to perform the subsequent steps to perform signaling by using the signaling manner; when it is determined that the uplink data to be sent is not small data, the terminal device performs the data manner. transmission. If the data is transmitted in the existing normal process, the user plane RAB needs to be established. For the process, refer to the existing process, which is not described in detail in this embodiment.
  • Step 102 The terminal device sends an RRC connection request message to the base station, where the RRC connection request message includes indication information indicating that the base station only establishes a signaling connection for the terminal device.
  • the foregoing indication information may be carried by using the “establishment cause value” cell in the RRC connection request message, but is not limited thereto.
  • the terminal device may also extend a new field in the RRC connection request message, or add a new information element (Information Element, IE for short) to the existing field to carry the indication information.
  • Information Element Information Element
  • Step 103 The terminal device receives an RRC connection setup message sent by the base station.
  • Step 104 The terminal device carries the uplink data in the RRC connection complete message and sends the uplink data to the base station, so that the base station passes the uplink data through the first type between the base station and the MME according to the foregoing indication information.
  • the first signaling message is sent to the MME, so that the MME sends the uplink data to the application server corresponding to the uplink data by using the first signaling message of the second type between the MME and the P-CSCF.
  • the foregoing step 102-step 104 describes the process in which the terminal device establishes an RRC connection with the base station, and sends the uplink data to the base station by using a signaling message with the base station, and at the same time, the terminal device indicates the process of establishing an RRC connection with the base station.
  • the base station establishes a signaling connection only for the terminal device, so that the base station and the network element (here mainly referred to as the MME) in the core network only establish a signaling connection for the terminal device, which lays a foundation for the terminal device to send uplink data to the application server through signaling. .
  • the base station After receiving the uplink data sent by the terminal device, the base station carries the uplink data in a signaling message between the MME and the MME, and sends the uplink data to the MME.
  • the MME in this embodiment is connected to the P-CSCF. Therefore, after receiving the uplink data sent by the base station through the signaling message, the MME carries the uplink data between the P-CSCF and the P-CSCF. The message is sent to the P-CSCF, so that the P-CSCF finally sends the uplink data to the application server via the S-CSCF.
  • the signaling protocol used between the base station and the MME is referred to as a first type of signaling protocol, and the signaling message under the first type of signaling protocol is referred to as a first type of signaling message;
  • the signaling protocol used between the P-CSCF and the P-CSCF is referred to as the second type of signaling protocol, and the signaling message under the second type of signaling protocol is referred to as the second type of signaling message.
  • the first, second, third, fourth, fifth, etc. numbers are respectively preceded by the first type of signaling messages, and the same reason, in order to distinguish the second type of each
  • the signaling message is also preceded by the first, second, third, fourth, fifth, etc. numbers in front of the second type of signaling message.
  • the numbers "first, second, third, fourth, fifth" here do not have a meaning, nor do they indicate sequential order, just to facilitate the distinction.
  • the foregoing first type of signaling protocol and the second type of signaling protocol may be the same signaling protocol, or may be different signaling protocols.
  • the first type of signaling protocol is a Non Access Stratum (NAS) protocol
  • the second type of signaling protocol is SIP.
  • the terminal device determines that the uplink data to be sent is small data, it determines to select signaling to perform transmission, and then, in the process of establishing an RRC connection with the base station, instructs the base station to establish signaling only for the terminal device.
  • the terminal device determines to select signaling to perform transmission, and then, in the process of establishing an RRC connection with the base station, instructs the base station to establish signaling only for the terminal device.
  • the user plane RAB does not need to be established between the MME and the terminal device, and the other resources required for transmitting the small data are not reserved for the terminal device, the network resources are solved, and the network resources are fully utilized for the big data. Transmission.
  • the terminal device in order to save radio resources and reduce power consumption of the terminal device, if the terminal device does not perform service interaction with the network side for a period of time, that is, no signaling interaction and user plane RAB interaction, the network side releases.
  • the terminal device is in an idle state (Idle State in English).
  • the terminal device needs to be restored first. Connect with the signaling on the network side, and then restore the user plane RAB with the network side through the signaling connection. At this time, the terminal device will be in the connected state (English is Connected State).
  • the service only needs to transmit a small amount of user plane data for each service.
  • the terminal device in the idle state needs to perform a recovery signaling connection every time, and then restore the air interface side user through the signaling connection.
  • Face RAB which increases signaling overhead, increases network load, and increases operator operating costs.
  • the method in this embodiment performs small data transmission by signaling, and does not need to establish a user plane RAB, and thus does not need to restore the user plane RAB, which can solve the above problem, is beneficial to reducing the network burden, reducing the operating cost of the operator, and is beneficial to the operation. Increase the transfer rate of small data.
  • the terminal device or the MME replaces the terminal device and needs to register with the application server. Based on this, in an optional implementation manner, before determining, by the terminal device, that the amount of data of the uplink data to be sent is less than a preset data volume threshold, the terminal device may include:
  • the terminal device sends an attach request message to the MME, so that the MME sends the first SIP registration request message to the application server by using the second type of second signaling message between the MME and the P-CSCF.
  • the attach request message includes an identifier of the terminal device, such as an identification terminal device may be an international mobile subscriber identification of another terminal apparatus 1 J code (International Mobile Subscriberldentification Number, abbreviated as IMSI).
  • the first SIP registration request message includes the identifier of the foregoing terminal device and a SIP identifier corresponding to the terminal device.
  • the terminal device receives an attach accept message sent by the MME, and the attach accept message is generated by the MME receiving the first SIP registration complete message returned by the application server by using the second type signaling message of the second type between the MME and the P-CSCF, where A SIP registration completion message is returned by the application server after receiving the SIP identifier corresponding to the terminal device.
  • the foregoing process is a process for the terminal device to perform an EPS attach process.
  • the The attach process includes authentication and location update operations, but does not create a default bearer, ie, the terminal device and
  • the MME interacts with the IMS system and the AS as a user agent (the English agent), and replaces the terminal device to complete the registration process with the application server, and the MME replaces the terminal device with the application server to register with the terminal device and the MME.
  • the first type of signaling interaction between is not affected.
  • the terminal device does not need an IP address, and the terminal device does not need to store its corresponding SIP identifier.
  • the SIP identifier corresponding to the terminal device in the first SIP registration request message may be that the HSS is returned to the MME in the attaching process, and the mapping relationship between the identifier of the terminal device and the SIP identifier corresponding to the terminal device is stored in the HSS.
  • the SIP identifier corresponding to the terminal device in the first SIP registration request message may also be allocated by the MME to the terminal device according to the identifier of the terminal device.
  • the terminal device or the MME replaces the terminal device and needs to register with the application server. Based on this, in another optional implementation manner, before determining, by the terminal device, whether the amount of data of the uplink data to be sent is less than a preset data volume threshold, the terminal device may include:
  • the terminal device sends an attach request message to the MME, where the attach request message includes an identifier of the terminal device.
  • the terminal device receives an attach accept message sent by the MME, where the attach accept message includes an IP address allocated by the MME for the terminal device.
  • the terminal device sends a first SIP registration request message to the MME by using the second signaling message of the first type between the terminal device and the MME according to the IP address allocated by the MME, so that the MME passes between the MME and the P-CSCF.
  • the second type of second signaling message sends the first SIP registration request message to the application server.
  • the first SIP registration request message includes an identifier of the terminal device and a SIP identifier corresponding to the terminal device.
  • the terminal device receives the first SIP registration completion message returned by the MME by using the first type of the third signaling message between the terminal device and the MME, where the first SIP registration completion message is after the application server receives the SIP identifier corresponding to the terminal device. return.
  • the MME receives the first SIP registration complete message by using the second type of third signaling message between the MME and the P-CSCF.
  • the foregoing process is a process for the terminal device to perform an EPS attach process.
  • the attach process includes an authentication and a location update operation, but does not create a default bearer, that is, only a signaling connection exists between the terminal device and the MME.
  • the MME assigns an IP address to the terminal device, and the terminal device pre-stores the SIP identifier corresponding to the terminal device, and the terminal device itself
  • the user agent initiates a SIP registration process to the application server, and encapsulates the first SIP registration request message in the first type of signaling message to the MME, and then passes the second type between the MME and the P-CSCF.
  • the signaling message is transmitted to the application server, thereby implementing the SIP registration process, and laying a foundation for subsequent data transmission between the terminal device and the application server.
  • the manner in which the terminal device pre-stores the corresponding SIP identifier includes, but is not limited to: the terminal device presets the corresponding SIP identifier at the factory, or the network side (mainly refers to the P-CSCF) sends a signaling message to the terminal device in advance. Configure the corresponding SIP ID for it.
  • the terminal device or the MME replaces the terminal device with the application server. Based on this, in another optional test mode, the terminal device may include: before determining whether the data volume of the uplink data to be sent is less than a preset data volume threshold:
  • the terminal device sends an attach request message to the MME, where the attach request message includes an identifier of the terminal device.
  • the terminal device receives the attach accept message sent by the MME.
  • the foregoing process is a process in which the terminal device performs an EPS attach process.
  • the attach process includes an authentication and a location update operation, but does not create a default bearer, that is, only a signaling connection exists between the terminal device and the MME.
  • the MME registers with the application server in advance, and each terminal device in the MME is no longer required to register with the application server, which reduces the number of registrations to the application server and saves resources.
  • the terminal device may receive the downlink data sent by the application server, in addition to sending the uplink data to the application server.
  • the process of the terminal device receiving the downlink data sent by the application server may include:
  • the terminal device receives the paging message sent by the MME, and the paging message is generated by the MME after receiving the downlink data sent by the application server to the terminal device by using the fourth type of the fourth signaling message between the MME and the P-CSCF.
  • the terminal device sends a service request message to the MME according to the foregoing paging message, where the service request message is used to indicate that the MME only establishes a signaling connection for the terminal device.
  • the terminal device receives the fourth signaling message of the first type that is sent by the MME according to the service request message, where the fourth signaling message of the first type includes the downlink data.
  • the downlink data sent by the application server to the terminal device is also passed through the MME through the second type of signaling message between the P-CSCF and the MME and the terminal device.
  • a type of signaling message is completed, and only a signaling connection exists between the MME and the terminal device, and the user plane RAB is not required to be established for the terminal device, which is also beneficial for saving network resources.
  • the interaction between the terminal device and the MME needs to be performed by the base station. Since the base station only plays a relay role in the above processes, it is omitted for simplifying the description.
  • FIG. 3 is a flowchart of a data transmission method according to another embodiment of the present invention. This embodiment will be described from the perspective of a base station. As shown in FIG. 3, the method in this embodiment includes:
  • Step 301 The base station receives an RRC connection request message sent by the terminal device, where the RRC connection request message is generated when the terminal device determines that the data volume of the uplink data to be sent is less than a preset data volume threshold, where the RRC connection request message includes indicating that the base station only An indication of establishing a signaling connection for the terminal device.
  • Step 302 The base station sends an RRC connection setup message to the terminal device.
  • Step 303 The base station receives an RRC connection complete message sent by the terminal device, where the RRC connection complete message includes the uplink data.
  • Step 304 The base station sends the uplink data to the MME by using the first signaling message of the first type between the base station and the MME according to the foregoing indication information, so that the MME passes the second type between the MME and the P-CSCF.
  • the first signaling message sends the uplink data to the application server corresponding to the uplink data.
  • the terminal device when the terminal device needs to send the uplink data to the application server, it is determined whether the data volume of the uplink data to be sent is small data, and the determining process is specifically determining whether the data volume of the uplink data to be sent is less than a preset data volume threshold. If the judgment result is yes, the uplink data to be sent is small data. If the judgment result is no, the uplink data to be sent is not small data (that is, big data). When it is determined that the uplink data to be sent is small data, the terminal device selects to transmit by using signaling.
  • the terminal device sends an RRC connection request message to the base station to request to establish an RRC connection with the base station, and at the same time, the carrying indication information indicates that the base station only establishes a signaling connection for the terminal device.
  • the base station receives the RRC connection request message sent by the terminal device, and sends an RRC connection setup message to the terminal device to establish an RRC with the terminal device.
  • the terminal device after receiving the RRC connection setup message, the terminal device sends the uplink data to the base station by using an RRC connection complete message.
  • the base station sends the uplink data to the MME by using the first type of first signaling message between the MME and the MME, and the MME passes the second type of first signaling between the MME and the P-CSCF.
  • the message is sent to the P-CSCF, and the P-CSCF sends the uplink data to the application server through the S-CSCF to complete the uplink data transmission.
  • the uplink data sent by the terminal device to the application server is a signaling message between the terminal device and the base station (ie, an RRC connection complete message), a signaling message between the base station and the MME, and The signaling message between the MME and the P-CSCF is transmitted, so that only the signaling connection needs to exist between the MME and the terminal device, and there is no need to establish a user plane RAB for the terminal device, and there is no need to reserve the transmission of small data for the terminal device.
  • Other resources save network resources and help increase the transmission rate of small data.
  • FIG. 4 is a flowchart of a data transmission method according to another embodiment of the present invention. This embodiment is a description from the perspective of the MME. As shown in FIG. 4, the method in this embodiment includes:
  • Step 401 The MME receives a first type of first signaling message sent by the base station, where the first type of the first signaling message is an RRC connection sent by the terminal device after receiving the RRC connection complete message sent by the terminal device.
  • the RRC connection completion message generated by the request message includes the uplink data sent by the terminal device to the application server, where the first type of the first signaling message includes the uplink data, and the indication information is used to indicate that the base station is only
  • the terminal device establishes a signaling connection.
  • Step 402 The MME sends the uplink data to the application server by using the first signaling message of the second type between the MME and the P-CSCF.
  • the terminal device when the terminal device needs to send the uplink data to the application server, it is determined whether the data volume of the uplink data to be sent is small data, and the determining process is specifically determining whether the data volume of the uplink data to be sent is less than a preset data volume threshold. If the judgment result is yes, the uplink data to be sent is small data. If the judgment result is no, the uplink data to be sent is not small data (that is, big data). When it is determined that the uplink data to be sent is small data, the terminal device selects to transmit by using signaling.
  • the terminal device sends an RRC connection request message to the base station to request to establish an RRC connection with the base station, and at the same time, the carrying indication information indicates that the base station only establishes a signaling connection for the terminal device.
  • the base station receives the RRC connection request message sent by the terminal device, and sends an RRC connection setup message to the terminal device to establish an RRC with the terminal device.
  • the terminal device after receiving the RRC connection setup message, the terminal device sends the uplink data to the base station by using an RRC connection complete message.
  • the base station After receiving the RRC connection complete message, the base station obtains the uplink data, and encapsulates the uplink data in the first signaling message of the first type between the base station and the MME to send to the MME.
  • the MME is connected. Receiving a first type of first signaling message, obtaining uplink data therefrom, and then encapsulating the uplink data in a first type of first signaling message between the P-CSCF and the P-CSCF to send to the P-CSCF, thereby enabling P- The CSCF sends the uplink data to the application server through the S-CSCF to complete the transmission of the uplink data.
  • the uplink data sent by the terminal device to the application server is a signaling message between the terminal device and the base station (ie, an RRC connection complete message), a signaling message between the base station and the MME, and The signaling message between the MME and the P-CSCF is transmitted, so that only the signaling connection needs to exist between the MME and the terminal device, and there is no need to establish a user plane RAB for the terminal device, and there is no need to reserve the transmission of small data for the terminal device.
  • Other resources save network resources and help increase the transmission rate of small data.
  • the terminal device or the MME replaces the terminal device and needs to register with the application server. Based on this, in another optional mode, the MME may include: before receiving the first signaling message of the first type sent by the base station:
  • the MME receives an attach request message sent by the terminal device, where the attach request message includes an identifier of the terminal device.
  • the identifier of the terminal device may be the IMSI of the terminal device, but is not limited thereto.
  • the MME obtains the SIP identifier corresponding to the terminal device according to the identifier of the terminal device, and generates a first SIP registration request message, where the first SIP registration request message includes the identifier of the terminal device and the SIP identifier corresponding to the terminal device.
  • the MME obtains the SIP identifier corresponding to the terminal device according to the identifier of the terminal device, but is not limited to the following manners:
  • the MME sends a Location Update Request message to the HSS, where the Location Update Request message includes the identity of the terminal device.
  • the MME receives a mapping relationship between the identifier of the terminal device returned by the HSS according to the identifier of the terminal device and the SIP identifier corresponding to the terminal device. Based on this, the MME obtains the SIP identifier corresponding to the terminal device from the mapping relationship between the identifier of the terminal device and the SIP identifier corresponding to the terminal device. Alternatively, the MME generates a SIP identifier corresponding to the terminal device according to the identifier of the terminal device.
  • the MME sends a first SIP registration request message to the application server through the second type of second signaling message between the MME and the P-CSCF.
  • the MME receives the first SIP registration complete message returned by the application server after receiving the SIP identifier corresponding to the terminal device by using the second signaling message of the second type between the MME and the P-CSCF. Then, the MME sends an attach accept message to the terminal device, and the attach accept message includes a first SIP registration complete message.
  • the foregoing process is a process in which the terminal device performs an EPS attach process.
  • the attach process includes an authentication and a location update operation, but does not create a default bearer, that is, only a signaling connection exists between the terminal device and the MME.
  • the MME interacts with the IMS system and the AS as a user agent (the English agent), and replaces the terminal device to complete the registration process with the application server, and the MME replaces the terminal device with the application server to register with the terminal device and the MME.
  • the first type of signaling interaction between is not affected.
  • the terminal device does not need an IP address, and the terminal device does not need to store its corresponding SIP identifier.
  • the terminal device or the MME replaces the terminal device and needs to register with the application server. Based on this, in another optional mode, the MME may include: before receiving the first signaling message of the first type sent by the base station:
  • the MME receives an attach request message sent by the terminal device, where the attach request message includes an identifier of the terminal device.
  • the MME assigns an IP address to the terminal device.
  • the MME sends an attach accept message to the terminal device, the attach accept message including an IP address.
  • the MME receives the second signaling message of the first type that is sent by the terminal device according to the IP address, where the second signaling message of the first type includes a first SIP registration request message, where the first SIP registration request message includes an identifier of the terminal device.
  • the SIP identifier corresponding to the terminal device.
  • the terminal device encapsulates the identifier of the terminal device and the pre-stored SIP identifier on the terminal device in the first SIP registration request message.
  • the method for pre-storing the SIP identifier on the terminal device includes, but is not limited to: the terminal device presets the corresponding SIP identifier at the factory, or the network side (mainly refers to the P-CSCF) sends a signaling message to the terminal device in advance. Configure the corresponding SIP ID.
  • the MME sends the first SIP registration request message to the application server by using the second type of second signaling message between the MME and the P-CSCF.
  • the MME receives the first SIP registration complete message returned by the application server after receiving the SIP identifier corresponding to the terminal device by using the second type of third signaling message between the MME and the P-CSCF.
  • the MME sends a third type of signaling message of the first type to the terminal device, and the third type of signaling message of the first type includes a first SIP registration complete message.
  • the foregoing process is a process for the terminal device to perform an EPS attach process.
  • the The attach process includes authentication and location update operations, but does not create a default bearer, ie, the terminal device and
  • the MME assigns an IP address to the terminal device, and the terminal device pre-stores the SIP identifier corresponding to the terminal device, and the terminal device itself acts as a user agent to initiate a SIP registration process to the application server, and the terminal device generates the first a SIP registration request message, which is then encapsulated in a first type of signaling message and sent to the MME, where the MME receives the first type of signaling message encapsulated with the first SIP registration request message, and then passes through the P-CSCF
  • the second type of signaling message is transmitted to the application server, thereby implementing a SIP registration process, which lays a foundation for subsequent data transmission between the terminal device and the application server.
  • the terminal device or the MME registers with the application server instead of the terminal device. Based on this, in an optional trial mode, before the MME receives the first signaling message of the first type sent by the base station, the MME may include:
  • the MME sends a second SIP registration request message to the P-CSCF by using the second signaling message of the second type between the MME and the P-CSCF, so that the P-CSCF sends the second SIP registration request message to the application server, where
  • the second type of the second signaling message includes a second SIP registration request message, where the second SIP registration request message includes an identifier of the MME and a SIP identifier corresponding to the MME.
  • the MME receives the second SIP registration complete message returned by the application server after receiving the SIP identifier corresponding to the MME, by using the second type of the third signaling message between the MME and the P-CSCF.
  • the foregoing process is a process in which the MME registers with the application server, in which the MME registers its own identity and the corresponding SIP identity to the application server.
  • the MME after receiving the second SIP registration completion message returned by the application server after receiving the SIP identifier corresponding to the MME, by using the second signaling message of the second type between the MME and the P-CSCF, includes:
  • the MME sends an attach accept message to the terminal device.
  • the foregoing process is a process in which the terminal device performs an EPS attach procedure after the MME completes the SIP registration process to the application server.
  • the attach process includes an authentication and a location update operation, but does not create a default bearer, that is, the terminal.
  • the terminal device may receive the downlink data sent by the application server, in addition to sending the uplink data to the application server.
  • the downlink data sent by the application server to the terminal device is also transmitted through the signaling message between the MME and the P-CSCF. It is not necessary to establish a user plane RAB for the terminal device, which is also beneficial for saving network resources.
  • the transmission process of downlink data includes:
  • the MME receives the downlink data sent by the application server to the terminal device by using the fourth type of fourth signaling message between the MME and the P-CSCF.
  • the MME sends a paging message to the terminal device.
  • the MME receives the service request message sent by the terminal device.
  • the MME sends a fourth type of signaling message of the first type to the terminal device, and the fourth type of signaling message of the first type includes downlink data.
  • the downlink data is sent to the S-CSCF, and the S-CSCF sends the downlink data to the P-CSCF.
  • the P-CSCF encapsulates the downlink data in the second.
  • a fourth type of signaling message is sent to the MME.
  • the MME receives the second type of fourth signaling message, and parses the downlink data therefrom.
  • the MME sends a paging message to the terminal device to inform the terminal device that downlink data needs to be sent to it.
  • the terminal device After receiving the paging message, the terminal device sends a service request message to the MME to request the MME to transmit downlink data to it.
  • the MME After receiving the service request message, the MME encapsulates the downlink data in the fourth type of signaling message between the terminal and the terminal device and sends the data to the terminal device. Therefore, the downlink data sent by the application server to the terminal device is also transmitted through the signaling message between the MME and the P-CSCF and between the MME and the terminal device, and the user plane RAB is not required to be established for the terminal device, and the network can also be saved. Resources.
  • the MME in order to complete the transmission of uplink data or downlink data, the MME is required to support both the first type of signaling protocol and the second type of signaling protocol. If the first type of signaling protocol and the second type of signaling protocol are different, the MME needs to be modified to support both the first type of signaling protocol and the second type of signaling protocol. In order to reduce the modification to the MME, the second type of signaling protocol can be supported in the prior art, and the network element interconnected with the MME has been implemented, and the connection between the MME and the P-CSCF is established through the network element. , reducing changes to the MME.
  • the first type of signaling protocol is the NAS protocol
  • the second type of signaling protocol is SIP.
  • the mobile switching center Mobile Switching Center
  • the MSC mobile switching center
  • FIG. 5 is a schematic diagram of another system architecture for implementing small data transmission based on embodiments of the present invention.
  • Figure 5 is compared with Figure 1. The difference is that the MME and the P-CSCF are connected through the MSC server.
  • the interface between the MME and the MSC server is called the SGs interface.
  • the MSC server has implemented a connection with the MME, and the MSC server supports the second type of signaling protocol, and the interconnection with the P-CSCF has also been implemented.
  • the MME sends the uplink data to the application server by using the first type of the first signaling message between the MME and the P-CSCF, and the MME sends the first type of the first signaling message to the MSC server.
  • the third type of first signaling message includes uplink data, so that the MSC server encapsulates the uplink data in the first type of first signaling message and sends the uplink data to the P-CSCF to send the uplink data to the application server.
  • the MME receiving the downlink data sent by the application server to the terminal device by using the fourth signaling message of the second type between the MME and the P-CSCF includes: receiving, by the MME, a third type of second signaling message sent by the MSC server
  • the third type of second signaling message is generated by the MSC server according to the second type of fourth signaling message sent by the P-CSCF, and the third type of second signaling message includes the downlink data.
  • the above third type of signaling protocol may be a first type of signaling protocol, such as a NAS protocol, or may be a different signaling protocol than the first type.
  • the existing MME can already support the third type of signaling protocol.
  • the MSC server implements the interaction between the MME and the P-CSCF, reducing the changes to the MME.
  • FIG. 6 is a flowchart of a data transmission method according to another embodiment of the present invention. This embodiment is a description from the perspective of the P-CSCF. As shown in FIG. 6, the method in this embodiment includes:
  • Step 601 The P-CSCF receives the first type of the first signaling message between the P-CSCF and the MME, and receives the uplink data sent by the terminal device to the application server, where the first type of the first signaling message is received by the MME.
  • the first signaling message of the first type sent by the base station is generated, according to the uplink data in the first signaling message of the first type, the first type of the first signaling message includes the uplink data, and the data of the uplink data. The amount is less than the preset data amount threshold.
  • Step 602 The P-CSCF sends the uplink data to the S-CSCF, so that the S-CSCF sends the uplink data to the application server.
  • the terminal device needs to send the uplink data to the application server, it is determined whether the data volume of the uplink data to be sent is small data, and the determining process is specifically determining whether the data volume of the uplink data to be sent is less than a preset data volume threshold. If the judgment result is yes, the uplink data to be sent is small data. If the judgment result is no, the uplink data to be sent is not small data (that is, big data).
  • the terminal device selects to transmit by using signaling.
  • the terminal device sends an RRC connection request message to the base station to request to establish an RRC connection with the base station, and at the same time, the carrying indication information indicates that the base station only establishes a signaling connection for the terminal device.
  • the base station receives the RRC connection request message sent by the terminal device, and sends an RRC connection setup message to the terminal device to establish an RRC with the terminal device.
  • the terminal device after receiving the RRC connection setup message, the terminal device sends the uplink data to the base station by using an RRC connection complete message.
  • the base station After receiving the RRC connection complete message, the base station obtains the uplink data, and encapsulates the uplink data in the first signaling message of the first type between the base station and the MME to send to the MME.
  • the MME receives the first type of first signaling message, obtains uplink data therefrom, and then encapsulates the uplink data in a first type of first signaling message between the P-CSCF and the P-CSCF.
  • the P-CSCF receives the first type of the first signaling message, obtains the uplink data, and then sends the uplink data to the S-CSCF, so that the S-CSCF sends the uplink data to the application server to complete the uplink data transmission. .
  • the uplink data sent by the terminal device to the application server is a signaling message between the terminal device and the base station (ie, an RRC connection complete message), a signaling message between the base station and the MME, and The signaling message between the MME and the P-CSCF is transmitted, so that only the signaling connection needs to exist between the MME and the terminal device, and there is no need to establish a user plane RAB for the terminal device, and there is no need to reserve the transmission of small data for the terminal device.
  • Other resources save network resources and help increase the transmission rate of small data.
  • the terminal device or the MME replaces the terminal device and needs to register with the application server in advance.
  • the P-CSCF before receiving the uplink data sent by the terminal device to the application server, by using the first type of the first signaling message between the P-CSCF and the MME, includes:
  • the P-CSCF receives the first SIP registration request message sent by the MME by using the second signaling message of the second type between the P-CSCF and the MME, where the first SIP registration request message includes the identifier of the terminal device and the SIP corresponding to the terminal device. logo.
  • the P-CSCF sends a first SIP registration request message to the S-CSCF, so that the S-CSCF sends the first SIP registration request message to the application server.
  • the P-CSCF receives the first SIP registration complete message returned by the application server sent by the S-CSCF after receiving the SIP identifier corresponding to the terminal device.
  • the P-CSCF sends a first SIP registration complete message to the MME through a second type of third signaling message between the P-CSCF and the MME.
  • the above process is a process in which the terminal device registers with the application server.
  • the registration process may be performed by the terminal device in the process of performing the EPS attachment process, and the MME acts as a user agent (the user agent in English) to interact with the IMS system and the application server, instead of the registration process performed by the terminal device to the application server.
  • the process of registering the MME with the application server instead of the terminal device does not affect the first type of signaling interaction between the terminal device and the MME.
  • the terminal device does not need an IP address, and the terminal device does not need to store its corresponding SIP identifier.
  • the first SIP registration request message is generated by the MME, and the SIP identifier corresponding to the terminal device in the first SIP registration request message may be returned to the MME by the HSS in the attaching process, where the identifier and the terminal device of the terminal device are stored on the HSS.
  • the mapping relationship between the corresponding SIP identifiers; or the SIP identifier corresponding to the terminal device in the first SIP registration request message may also be allocated by the MME to the terminal device according to the identifier of the terminal device.
  • the foregoing registration process may also be a SIP registration process initiated by the terminal device itself as a user agent to the application server after the MME allocates an IP address to the terminal device in the EPS attaching process.
  • the first SIP registration request message is generated by the terminal device and then sent to the MME.
  • the SIP identifier corresponding to the terminal device in the first SIP registration request message may be pre-stored on the terminal device.
  • the terminal device or the MME replaces the terminal device and needs to register with the application server in advance.
  • the P-CSCF before receiving the uplink data sent by the terminal device to the application server, by using the first type of the first signaling message between the P-CSCF and the MME, includes:
  • the P-CSCF receives the second SIP registration request message sent by the MME by using the second type of the second signaling message between the P-CSCF and the MME, where the second SIP registration request message includes the identifier of the MME and the SIP identifier corresponding to the MME.
  • the P-CSCF sends a second SIP registration request message to the S-CSCF, so that the S-CSCF will be the second
  • the SIP registration request message is sent to the application server.
  • the P-CSCF receives the second SIP registration complete message returned by the application server sent by the S-CSCF after receiving the SIP identifier corresponding to the MME.
  • the P-CSCF sends a second SIP registration complete message to the MME through a second type of third signaling message between the P-CSCF and the MME.
  • the above is a process in which the MME performs SIP registration as a user agent to the application server before the terminal device performs the attach procedure.
  • the second SIP registration request message is generated and sent by the MME.
  • the MME registers with the application server in advance, and each terminal device in the MME is no longer required to register with the application server, which can reduce the number of registrations to the application server and save resources.
  • the terminal device may receive the downlink data sent by the application server, in addition to sending the uplink data to the application server.
  • the process of the downlink data sent by the application server to the terminal device includes: the P-CSCF receives the downlink data sent by the application server sent by the S-CSCF to the terminal device and the address information of the MME; and then, the P-CSCF passes the P according to the address information of the MME.
  • the second type of fourth signaling message between the CSCF and the MME sends downlink data to the MME.
  • the address information of the MME is obtained by the S-CSCF according to the SIP identifier corresponding to the terminal device, and the HSS stores the mapping relationship between the identifier of the terminal device and the SIP identifier corresponding to the terminal device, and the identifier of the terminal device and the MME.
  • the mapping relationship between address information Specifically, the S-CSCF queries the HSS according to the SIP identifier corresponding to the terminal device, obtains the identifier of the terminal device, and then obtains the address information of the MME according to the identifier of the terminal device.
  • the P-CSCF receives the uplink data sent by the terminal device to the application server by using the first signaling message of the second type between the P-CSCF and the MME, where the P-CSCF receives the MSC server.
  • the second signaling message is generated by the MSC server according to the third type of first signaling message sent by the MME, and the third type of first signaling message includes the uplink data.
  • the P-CSCF sends the downlink data to the MME by using the second type of the fourth signaling message between the P-CSCF and the MME according to the address information of the MME, including: the second type that the P-CSCF sends to the MSC server.
  • the fourth signaling message is sent to the MME by the MSC server to encapsulate the downlink data in the fourth type of the fourth signaling message in the third type of the second signaling message. It can be seen from the above that the downlink data sent by the application server to the terminal device is also completed by the MME through the second type of signaling message with the P-CSCF and the first type of signaling message between the MME and the terminal device. There is only a signaling connection between the MME and the terminal device, and it is not necessary to establish a user plane RAB for the terminal device, which is also beneficial for saving network resources.
  • FIG. 7 the system architecture for implementing small data transmission shown in FIG. 1 is specifically shown in FIG. 7.
  • NAS signaling is used between the network elements in the mobile core network, and the IMS system uses SIP.
  • SIP Session Initiation Protocol
  • FIG. 8 is a flowchart of a small data transmission method according to an embodiment of the present invention.
  • This embodiment takes an example in which the terminal device sends uplink data to the application server.
  • the method in this embodiment includes: Step 8: The terminal device determines whether the uplink data to be sent is small data, and determines that the uplink data to be sent is small data, and determines that the uplink data is small. Data is sent.
  • the terminal device may select to use the signaling mode or the data mode to send according to the data volume size. If the data volume of the uplink data to be sent is less than the preset data volume threshold, the terminal device selects the signaling mode; If the amount of data to be sent uplink data is greater than or equal to the preset data volume threshold, the terminal device selects a method for using the data. If the data is used, the normal process is used, that is, the user plane RAB needs to be established for the terminal device.
  • Step 8b The terminal device sends an RRC connection request message to the base station to request to establish an RRC connection.
  • the cell "establishment cause value" carried in the RRC connection request message indicates that the base station only establishes a signaling connection for the terminal device.
  • Step 8c The base station sends an RRC connection setup message to the terminal device, instructing the terminal device to establish an RRC connection.
  • Step 8d The terminal device sends an RRC connection complete message to the base station, where the RRC connection complete message carries a NAS data unit (PDU), and the uplink data to be sent is encapsulated in the NAS PDU.
  • PDU NAS data unit
  • maintains a signaling connection with the terminal device without creating or restoring the user plane RAB.
  • Step 8e The base station sends the NAS PDU to the MME by using an initial UE message.
  • the initial UE message is a NAS signaling message, which is equivalent to the first signaling message of the first type.
  • Step 8f The terminal device performs an authentication and security process by using the base station, the MME, the HSS, and the like. This process belongs to the prior art and will not be described here.
  • Step 8g The MME obtains uplink data from the initial UE message, and encapsulates the uplink data in a message (MESSAGE in English) message to the P-CSCF.
  • Step 8h the P-CSCF forwards the message (MESSAGE) message to the S-CSCF.
  • Step 8i The S-CSCF triggers the transmission of the information (MESSAGE) message to the SCS/AS based on the initial filtering criteria.
  • MESSAGE information
  • the MESSAGE message is a SIP signaling message, which is equivalent to the first signaling message of the second type.
  • the initial filter criteria provides service triggering capabilities.
  • the initial filtering criteria and the address of the specified application server AS have been downloaded to the corresponding S-CSCF.
  • the S-CSCF Based on the initial filtering criteria, the S-CSCF triggers the transmission of the message to the SCS/AS (MESSAGE) message, and forwards the information message to the designated AS application server.
  • SCS/AS SCS/AS
  • Step 8j The S-CSCF sends a 200 OK message to the P-CSCF.
  • Step 8k The P-CSCF forwards the 200 OK message to the MME.
  • the foregoing 200 OK message is a SIP signaling message, which is equivalent to the second type of the fifth signaling message, and is used to notify the P-CSCF, the MME, the terminal device, and the like that the uplink data has been successfully transmitted to the AS.
  • Step 81 The MME sends an acknowledgement message to the base station by using a downlink NAS transmission message.
  • the downlink NAS transmission message belongs to the NAS signaling message, and is equivalent to the fifth signaling message of the first type, and is used to carry the acknowledgement message to inform the base station and the terminal device that the uplink data has been successfully transmitted to the AS.
  • Step 8m The base station transmits an acknowledgement message to the terminal device by using a downlink information transmission message.
  • Step 8n If no other data is sent within the specified time, the base station releases the RRC connection with the terminal device and the S1 signaling connection with the MME.
  • FIG. 9A An optional registration process is shown in FIG. 9A, and specifically includes:
  • Step 9a The terminal device sends an attach request message to the MME, where the attach request message carries the IMSI of the terminal device.
  • Step 9b The MME performs an EPS attach process for the terminal device, where the attach process includes: an authentication and a location update operation, but does not create a default bearer.
  • the HSS may return the IMSI of the terminal device to the MME. Mapping relationship of SIP identifiers corresponding to terminal devices.
  • the terminal device does not need to store the corresponding SIP identifier, and only needs to add a mapping relationship between the IMSI of the terminal device and the SIP identifier corresponding to the terminal device in the subscription data, and store the mapping relationship to the HSS. Just go up.
  • the MME may generate, according to the IMSI of the terminal device, a SIP identifier corresponding to the terminal device.
  • Step 9c The MME determines that the terminal device needs to perform IMS registration, so the P-CSCF discovery process is initiated.
  • Step 9d The MME generates a first SIP registration request message by using the SIP identifier corresponding to the terminal device, and then encapsulates the P-CSCF that is found in the registration (English REGISTER) message to the P-CSCF found in the above step, that is, initiates a SIP registration process.
  • the first SIP registration request message includes an IMSI of the terminal device and a SIP identifier corresponding to the terminal device.
  • Step 9e The P-CSCF determines, according to the SIP identifier corresponding to the terminal device, that the terminal device is from the visited network, and is to be registered, so initiates a DNS query for the I-CSCF address in the home network of the terminal device to the DNS server. Then, according to the DNS query result, a registration (REGISTER) message is sent to the I-CSCF.
  • the part of the SIP identifier corresponding to the terminal device is used to identify the network from which the terminal device belongs (that is, the domain name corresponding to the network to which the terminal device belongs), and the domain name of the IMS network is also stored on the P-CSCF.
  • the P-CSCF can determine whether the terminal device is from the visited network according to the SIP identifier corresponding to the terminal device.
  • the so-called visited network refers to a network other than the IMS network to which the P-CSCF belongs.
  • Step 9f The I-CSCF sends a Cx query to the HSS.
  • Step 9g The HSS checks the registration status of the user corresponding to the terminal device, and confirms whether the user is allowed to register according to the subscription data, and the HSS returns a Cx query response, that is, the capability required to return the S-CSCF, and the I-CSCF selects an appropriate one according to the result returned by the HSS. S-CSCF.
  • Step 9h the I-CSCF sends a registration (REGISTER) message to the selected S-CSCF.
  • Step 9j The S-CSCF sends a REGISTER message to the AS to trigger registration with the SCS/AS.
  • Step 9k after receiving the registration (REGISTER) message, the SCS/AS returns to the S-CSCF. 200 ok message to complete the registration.
  • the registration message is a SIP signaling message, which is equivalent to the second signaling message of the second type.
  • Step 91 The S-CSCF returns a 200 ok message to the P-CSCF.
  • Step 9m the P-CSCF returns a 200 ok message to the MME.
  • the above 200 ok message carries a first SIP registration complete message, which is a SIP signaling message, which is equivalent to the second type of third signaling message.
  • Step 9n The MME sends an attach accept message to the terminal device, where the attach accept message includes a first SIP registration complete message.
  • the attaching process includes an authentication and a location update operation, etc., but does not create a default bearer, that is, only a signaling connection exists between the terminal device and the MME.
  • the MME interacts with the IMS system and the AS as a user agent (the English agent), and completes the registration process with the application server instead of the terminal device, and the MME replaces the terminal device with the application server to register the terminal device and the MME.
  • the first type of signaling interaction between is not affected. This embodiment lays the foundation for subsequent small data transmission.
  • FIG. 9B Another optional registration process is shown in FIG. 9B, which specifically includes:
  • Step 10a The terminal device sends an attach request message to the MME, where the attach request message carries the IMSI of the terminal device.
  • Step 10b The MME performs an EPS attach process for the terminal device, where the attach process includes: an authentication and a location update operation, but does not create a default bearer.
  • Step 10c The MME allocates an IP address to the terminal device.
  • Step 10d The MME sends an attach accept message to the terminal device, where the attach accept message carries an IP address allocated by the MME for the terminal device.
  • Step 10e The terminal device, as a user agent of the IMS, generates a SIP registration request message according to the IMSI of the locally stored terminal device and the corresponding SIP identifier, and encapsulates the SIP registration request message in the NAS registration message and sends the message to the NAS registration message.
  • MME The NAS registration message includes an IP address allocated by the MME for the terminal device and an IP address of the MME.
  • the NAS registration message is a SIP signaling message, which is equivalent to the first type of second signaling message.
  • Step 10f The MME extracts the first SIP registration request message from the NAS registration message, and encapsulates the message It is sent to the P-CSCF in the registration message.
  • Step 10g The P-CSCF determines, according to the SIP identifier corresponding to the terminal device, that the terminal device is from the visited network, and is to be registered, so initiates a DNS query for the I-CSCF address in the home network of the terminal device to the DNS server. Then, according to the DNS query result, a registration (REGISTER) message is sent to the I-CSCF.
  • step 10h the I-CSCF sends a Cx query to the HSS.
  • Step 10i The HSS checks the registration status of the user corresponding to the terminal device, and confirms whether the user is allowed to register according to the subscription data, and the HSS returns a Cx query response, that is, the capability required to return the S-CSCF, and the I-CSCF selects a suitable one according to the result returned by the HSS. S-CSCF.
  • Step 10j The I-CSCF sends a REGISTER message to the selected S-CSCF.
  • Step 10k After receiving the REGISTER message, the S-CSCF interacts with the HSS through the Cx interface to obtain an authentication vector and user subscription information.
  • Step 101 The S-CSCF sends a registration (REGISTER) message to the AS to trigger registration with the SCS/AS.
  • Step 10m After receiving the REGISTER message, the SCS/AS returns a 200 ok message to the S-CSCF to complete the registration.
  • the registration message is a SIP signaling message, which is equivalent to the second signaling message of the second type.
  • Step 10n The S-CSCF returns a 200 ok message to the P-CSCF.
  • Step 10o The P-CSCF returns a 200 ok message to the MME.
  • the above 200 ok message carries a first SIP registration complete message, which is a SIP signaling message, which is equivalent to the second type of third signaling message.
  • Step 10p The MME sends a 200 ok message to the terminal device, where the 200 ok message includes a first SIP registration complete message.
  • the 200 ok message in step 10p is a SIP signaling message, encapsulated in the NAS signaling message.
  • the MME sends to the terminal device, which is equivalent to the third signaling message of the first type.
  • the attaching process includes an authentication and a location update operation, but does not create a default bearer, that is, only a signaling connection exists between the terminal device and the MME.
  • the MME allocates an IP address to the terminal device, and the terminal device pre-stores the SIP identifier corresponding to the terminal device, and the terminal device itself initiates SIP registration to the application server as a user agent.
  • the process is implemented by encapsulating the first SIP registration request message in a first type of signaling message and sending the message to the MME, and then transmitting the second type of signaling message between the MME and the P-CSCF to the application server, thereby implementing SIP registration.
  • the process lays the foundation for the subsequent data transmission between the terminal device and the application server.
  • FIG. 9C Another optional registration process is shown in FIG. 9C, which specifically includes:
  • Step 1 la the MME determines to perform IMS registration, so initiates a P-CSCF discovery process.
  • Step l lb the MME generates a second SIP registration request message by using the SIP identifier corresponding to the MME, and then encapsulates it in the registration (English REGISTER) message and sends it to the P-CSCF discovered in the above step, that is, initiates the SIP registration process.
  • the second SIP registration request message includes an identifier of the MME and a SIP identifier corresponding to the MME.
  • Step 1 lc The P-CSCF determines that the MME is from the visited network according to the SIP identifier corresponding to the MME, and is to be registered, so the DNS query for the I-CSCF address in the home network of the MME is initiated to the DNS server, and then According to the DNS query result, a registration (REGISTER) message is sent to the I-CSCF.
  • Step l ld I-CSCF sends a Cx query to the HSS.
  • Step l the HSS checks the registration status of the MME, and confirms whether the MME is allowed to register according to the subscription data, and the HSS returns a Cx query response, that is, the capability required to return the S-CSCF, and the I-CSCF selects an appropriate S- according to the result returned by the HSS.
  • CSCF CSCF.
  • Step l lf I-CSCF sends a REGISTER message to the selected S-CSCF.
  • Step l After receiving the REGISTER message, the S-CSCF interacts with the HSS through the Cx interface to obtain an authentication vector and user subscription information.
  • Step l lh the S-CSCF sends a registration (REGISTER) message to the AS, triggering registration with the SCS/AS.
  • REGISTER Registration
  • Step l li SCS/AS returns a 200 ok message to the S-CSCF after receiving the REGISTER message to complete the registration.
  • the registration message is a SIP signaling message, which is equivalent to the second signaling message of the second type.
  • Step 1 lj the S-CSCF returns a 200 ok message to the P-CSCF.
  • Step 1 lk the P-CSCF returns a 200 ok message to the MME.
  • the above 200 ok message carries a first SIP registration complete message, which is a SIP signaling message.
  • a first SIP registration complete message which is a SIP signaling message.
  • the third signaling message of the second type described above corresponds to the third signaling message of the second type described above.
  • step I lk the method further includes:
  • Step 111 The terminal device sends an attach request message to the MME, where the attach request message carries the IMSI of the terminal device.
  • Step l lm the MME performs an EPS attach process for the terminal device, and the attach process includes: authentication and location update operations, but does not create a default bearer.
  • Step 1 ln the MME sends an attach accept message to the terminal device.
  • step 111-step l ln the authentication and location update operations are included, but the default bearer is not created, that is, only the signaling connection exists between the terminal device and the MME.
  • the MME interacts with the IMS system and the AS as a user agent, and replaces the terminal device to complete the registration process with the application server, and the MME replaces the terminal device with the application server to register the terminal device and the MME.
  • the first type of signaling interaction between is not affected. This embodiment lays the foundation for subsequent small data transmission.
  • the small data transmission method further includes: the SCS/AS transmitting downlink data to the terminal device.
  • the S-CSCF queries the routing information from the HSS, and sends the data to the MME, and the MME sends the data to the terminal device through the NAS signaling message.
  • the downlink data transmission process is as shown in FIG. 9D, and includes: Step 12a: The SCS/AS sends a message (MESSAGE) message to the S-CSCF, where the message (MESSAGE) message carries downlink data.
  • the downlink data carries a SIP identifier corresponding to the terminal device.
  • the SCS/AS After the MME completes the registration process, and the terminal device completes the EPS attach procedure, the SCS/AS sends the downlink data encapsulated information (MESSAGE) message sent to the terminal device to the S-CSCF.
  • MESSAGE downlink data encapsulated information
  • Step 12b The S-CSCF queries the HSS according to the SIP identifier corresponding to the terminal device, and obtains the identifier of the terminal device from the mapping relationship between the IMSI of the terminal device and the SIP identifier corresponding to the terminal device on the HSS, and further identifies the terminal device from the HSS.
  • the mapping relationship of the addresses of the MME the address of the MME is obtained.
  • Step 12c The S-CSCF sends the information (MESSAGE) message and the address of the MME to the P-CSCF according to the query result.
  • MESSAGE information
  • Step 12d The P-CSCF forwards the information (MESSAGE) message to the MME according to the address of the MME.
  • the information (MESSAGE) message is a SIP signaling message, which is equivalent to the fourth type of fourth signaling message.
  • Step 12e The MME queries the HSS according to the SIP identifier corresponding to the terminal device, and obtains the IMSI of the terminal device from the mapping relationship between the IMSI of the terminal device and the SIP identifier corresponding to the terminal device on the HSS, and sends a paging message to the terminal device, where the paging message is carried. Small data transfer instructions.
  • Step 12f The terminal device sends a service request message to the MME to establish a signaling connection.
  • Step 12g the terminal device, the MME, the HSS, and the like complete the authentication process.
  • Step 12h The MME extracts the downlink data to be sent from the received message (MESSAGE) message, and encapsulates the downlink data in the downlink NSA transmission message and sends the downlink data to the terminal device.
  • MESSAGE received message
  • the downlink NSA transmission message in step 12h is a NAS signaling message, which is equivalent to the fourth signaling message of the first type described above.
  • Step 12i The terminal device encapsulates the transmission response message in the uplink NAS transmission message and sends the message
  • Step 12j The MME sends a transmission response message to the P-CSCF.
  • Step 12k The P-CSCF sends a transmission response message to the S-CSCF.
  • Step 121 The S-CSCF sends a transmission response message to the SCS/AS.
  • Step 12m If no other data is sent within the specified time, the base station releases the RRC connection with the terminal device and the S1 signaling connection with the MME.
  • the uplink data and the downlink data between the terminal device and the application server are transmitted through signaling messages between the MME and the P-CSCF and between the MME and the terminal device, so that the terminal device is not required to be established.
  • the user plane RAB saves network resources, reduces network load, and helps to increase data transmission rate.
  • the interaction between the MME and the P-CSCF is implemented by the MSC server.
  • the terminal device sends the uplink data to the SCS/AS as an example.
  • the process of the SCS/AS transmitting the downlink data to the terminal device can be easily known by those skilled in the art according to the description of the related embodiments of the present invention.
  • another process of small data transmission includes:
  • Step 13a The terminal device determines whether the uplink data to be sent is small data, and determines that the uplink data to be sent is small data, and determines to send small data by means of signaling.
  • Step 13b The terminal device sends an RRC connection request message to the base station, requesting to establish an RRC connection. Then, the cell "establishment cause value" carried in the RRC connection request message indicates that the base station only establishes a signaling connection for the terminal device.
  • Step 13c The base station sends an RRC connection setup message to the terminal device, instructing the terminal device to establish an RRC connection.
  • Step 13d The terminal device sends an RRC connection complete message to the base station, where the RRC connection complete message carries the NAS PDU, and the uplink data to be sent is encapsulated in the NAS PDU.
  • Step 13e The base station sends the NAS PDU to the MME by using an initial UE message.
  • Step 13f The terminal device performs an authentication and security process by using the base station, the MME, and the HSS. This process belongs to the prior art and will not be described here.
  • Step 13g The MME obtains the uplink data from the initial UE message, encapsulates the uplink data in the uplink data sending message of the SGs interface, and sends the uplink data to the MSC server through the SGs interface with the MSC server.
  • Step 13h The MSC server obtains uplink data from the uplink data sending message of the SGs interface, and encapsulates the uplink data in the information (MESSAGE in English) message to send to the P-CSCF.
  • Step 13i the P-CSCF forwards the message (MESSAGE) message to the S-CSCF.
  • Step 13j The S-CSCF triggers the transmission of the information (MESSAGE) message to the SCS/AS based on the initial filtering criteria.
  • MESSAGE information
  • step 13k the S-CSCF sends an acknowledgement (OK) message to the P-CSCF.
  • Step 131 The P-CSCF forwards an acknowledgement (OK) message to the MSC server.
  • Step 13m The MSC server encapsulates the acknowledgement (OK) message in the downlink data sending message of the SGs interface, and sends the message to the MME through the SGs interface.
  • OK acknowledgement
  • Step 13n The MME sends an acknowledgement message to the base station by using a downlink NAS transmission message.
  • Step 13o The base station transmits an acknowledgement message to the terminal device by using a downlink information transmission message.
  • Step 13p If no other data is sent within the specified time, the base station releases the RRC connection with the terminal device and the S1 signaling connection with the MME.
  • FIG. 11 is a schematic structural diagram of a terminal device according to an embodiment of the present invention. As shown in FIG. 11, the terminal device of this embodiment includes: a determining module 111, a first sending module 112, and a first receiving module 113.
  • the determining module 111 is configured to determine whether the amount of data of the uplink data to be sent is less than a preset data volume threshold.
  • the first sending module 112 is connected to the determining module 111, and configured to send an RRC connection request message to the base station when the determining module 111 determines that the data volume of the uplink data is less than the preset data amount threshold, where the RRC connection request message includes indicating that the base station only An indication of establishing a signaling connection for the terminal device.
  • the first receiving module 113 is configured to receive an RRC connection setup message sent by the base station after the first sending module 112 sends the RRC connection request message.
  • the first receiving module 113 is connected to the first sending module 112.
  • the first sending module 112 of the embodiment is further configured to: after receiving the RRC connection setup message, the first receiving module 113, the uplink data is carried in the RRC connection complete message, and sent to the base station, so that the base station according to the indication information
  • the uplink data is sent to the MME by using the first type of first signaling message between the eNB and the MME, so that the MME sends the uplink data to the uplink data by using the first type of the first signaling message between the MME and the P-CSCF.
  • the corresponding application server is further configured to: after receiving the RRC connection setup message, the first receiving module 113, the uplink data is carried in the RRC connection complete message, and sent to the base station, so that the base station according to the indication information
  • the uplink data is sent to the MME by using the first type of first signaling message between the eNB and the MME, so that the MME sends the uplink data to the uplink data by using the first type of the first signaling message between the MME and
  • the first sending module 112 is further configured to send an attach request message to the MME before the determining module 111 determines whether the data volume of the uplink data to be sent is less than a preset data volume threshold, so that The MME sends a first SIP registration request message to the application server by using the second signaling message of the second type between the MME and the P-CSCF, where the attach request message includes an identifier of the terminal device, where the first SIP registration request message includes the terminal device Identifies the SIP identifier corresponding to the terminal device.
  • the first receiving module 113 is further configured to: after the first sending module 112 sends an attach request message to the MME, receive an attach accept message sent by the MME, where the attach accept message is a second type between the MME and the P-CSCF. After the third signaling message is received by the first SIP registration completion message returned by the application server, the first SIP registration completion message is returned by the application server after receiving the SIP identifier corresponding to the terminal device.
  • the terminal device of the present embodiment implements the SIP attaching process by the first sending module 112 and the first receiving module 113, and the terminal device of the embodiment is replaced by the MMS as the user agent to complete the SIP to the application server. registration process.
  • the terminal setting of the embodiment There is only a signaling connection between the standby and the MME.
  • the first sending module 112 is further configured to send an attach request message to the MME before the determining module 111 determines whether the data volume of the uplink data to be sent is less than a preset data volume threshold, and the attaching The request message includes an identifier of the terminal device, and after the first receiving module 113 receives the attach accept message sent by the MME, according to the IP address allocated by the MME for the terminal device in the attach accept message, the first between the terminal device and the MME
  • the first type of second signaling message is sent to the MME to send the first SIP registration request message to the MME, so that the MME sends the first SIP registration request message to the application by using the second type of second signaling message between the MME and the P-CSCF.
  • the server, the first SIP registration request message includes an identifier of the terminal device and a SIP identifier corresponding to the terminal device.
  • the first receiving module 113 is further configured to: after the first sending module 112 sends an attach request message to the MME, receive an attach accept message sent by the MME, where the attach accept message includes an IP address allocated by the MME for the terminal device; and After the sending module 112 sends the first SIP registration request message to the MME, the first SIP registration completion message returned by the MME is received by the first type of the third signaling message between the terminal device and the MME, where the first SIP registration is completed.
  • the message is returned by the application server after receiving the SIP identifier corresponding to the terminal device, and the MME receives the first SIP registration completion message by using the second type of third signaling message between the MME and the P-CSCF.
  • the terminal device in this embodiment implements a SIP registration process to the application server as a user agent in the EPS attach process by the first sending module 112 and the first receiving module 113. There is only a signaling connection between the terminal device and the MME in this embodiment.
  • the first sending module 112 is further configured to determine the module.
  • the method Before determining whether the data volume of the uplink data to be sent is less than the preset data volume threshold, the method sends an attach request message to the MME, where the attach request message includes an identifier of the terminal device.
  • the first receiving module 113 is further configured to: after the first sending module 112 sends an attach request message to the MME, receive an attach accept message sent by the MME.
  • the terminal device in this embodiment completes the EPS attach procedure by using the first sending module 112 and the first receiving module 113, and does not establish a default bearer in the EPS attaching process, that is, the terminal device and the MME in this embodiment. There is only a signaling connection between them.
  • the MME directly registers as a user agent with the application server.
  • the first receiving module 113 is further configured to receive a paging message sent by the MME, and receive the service request sent by the MME according to the first sending module 112.
  • the fourth type of fourth signaling message sent by the message is generated by the MME after receiving the downlink data sent by the application server to the terminal device by using the fourth type of the fourth signaling message between the MME and the P-CSCF, where the fourth type of the fourth signaling message includes: Downstream data.
  • the first sending module 112 is further configured to send a service request message to the MME after the first receiving module 113 receives the paging message, where the service request message is used to indicate that the MME only establishes a signaling connection for the terminal device.
  • the function modules of the terminal device provided in this embodiment may be used to perform the process of the data transmission method described above from the perspective of the terminal device.
  • the specific working principle is not described here. For details, refer to the description of the method embodiment.
  • the terminal device in this embodiment performs small data transmission based on the first type of signaling message between the MME and the terminal device and the second type of signaling message between the MME and the P-CSCF, without specifically establishing or restoring the terminal.
  • the device and the user plane RAB on the air interface side of the network save network resources, improve the transmission efficiency of small data, reduce signaling interaction between the terminal device and the network side, and reduce network load.
  • FIG. 12 is a schematic structural diagram of a terminal device according to another embodiment of the present invention. As shown in FIG. 12, the terminal device of this embodiment includes: a processor 121, a transmitter 122, and a receiver 123.
  • the processor 121 is configured to determine whether the amount of data of the uplink data to be sent is less than a preset data amount threshold.
  • the transmitter 122 is connected to the processor 121, and is configured to: when the processor 121 determines that the data volume of the uplink data is less than the preset data volume threshold, send an RRC connection request message to the base station, where the RRC connection request message includes the indication that the base station is only the terminal.
  • the device establishes an indication of the signaling connection.
  • the receiver 123 is configured to receive an RRC connection setup message sent by the base station after the transmitter 122 sends the RRC connection request message.
  • the transmitter 122 is coupled to the receiver 123.
  • the transmitter 122 is further configured to: after the receiver 123 receives the RRC connection setup message, send the uplink data to the base station in the RRC connection complete message, so that the base station passes the uplink data between the base station and the MME according to the indication information.
  • a type of the first signaling message is sent to the MME, so that the MME sends the uplink data to the application server corresponding to the uplink data by using the first type of the first signaling message between the MME and the P-CSCF.
  • the terminal device provided in this embodiment can be used to perform the foregoing data transmission method described in the perspective of the terminal device.
  • the specific working principle is not described here. For details, refer to the description of the method embodiment.
  • the terminal device of this embodiment is based on the first type of signaling cancellation between the MME and the terminal device.
  • the second type of signaling message between the MME and the P-CSCF performs small data transmission, and does not need to specifically establish or restore the user plane RAB of the terminal device and the network air interface side, thereby saving network resources and improving transmission of small data. Efficiency, reduce signaling interaction between the terminal device and the network side, and reduce network load.
  • FIG. 13 is a schematic structural diagram of a base station according to an embodiment of the present invention. As shown in FIG. 13, the base station of this embodiment includes: a second receiving module 131 and a second sending module 132.
  • the second receiving module 131 is configured to receive an RRC connection request message sent by the terminal device, and after the second sending module 132 sends the RRC connection setup message to the terminal device, receive an RRC connection complete message sent by the terminal device, where the RRC connection request message is sent.
  • the RRC connection request message includes indication information indicating that the base station only establishes a signaling connection for the terminal device, where the RRC connection complete message includes the uplink data.
  • the second receiving module 131 and the second sending module 132 are connected.
  • the second sending module 132 is configured to: after the second receiving module 131 receives the RRC connection request message, send an RRC connection setup message to the terminal device, and after the second receiving module 131 receives the RRC connection complete message, according to the indication information, Sending uplink data to the MME by using the first type of first signaling message between the base station and the MME, so that the MME passes the MME and the P-CSCF.
  • the function modules of the base station provided in this embodiment may be used to perform the foregoing process of the data transmission method described in the perspective of the base station.
  • the specific working principle is not described here. For details, refer to the description of the method embodiment.
  • the base station in this embodiment cooperates with the terminal device provided in the foregoing embodiment, and is based on a first type of signaling message between the MME and the terminal device and a second type of signaling message between the MME and the P-CSCF.
  • the data transmission does not need to specifically establish or restore the user plane RAB of the terminal device and the network air interface side, which saves network resources, improves the transmission efficiency of small data, reduces signaling interaction between the terminal device and the network side, and reduces network load.
  • FIG. 14 is a schematic structural diagram of a base station according to another embodiment of the present invention. As shown in FIG. 14, the base station of this embodiment includes: a receiver 141 and a transmitter 142.
  • the receiver 141 is configured to receive an RRC connection request message sent by the terminal device, and after the transmitter 142 sends the RRC connection setup message to the terminal device, receive an RRC connection complete message sent by the terminal device, where the RRC connection request message is determined by the terminal device.
  • the RRC connection request message includes indicating that the base station is only the end
  • the end device establishes indication information of the signaling connection, and the RRC connection complete message includes uplink data.
  • the transmitter 142 is configured to: after the receiver 141 receives the RRC connection request message, send an RRC connection setup message to the terminal device, and after the receiver 141 receives the RRC connection complete message, according to the indication information, pass between the base station and the MME.
  • the first signaling message of the first type sends the uplink data to the MME, so that the MME sends the uplink data to the application server corresponding to the uplink data by using the first signaling message of the second type between the MME and the P-CSCF.
  • the base station provided by this embodiment can be used to perform the foregoing data transmission method described in the perspective of the base station.
  • the specific working principle is not described here. For details, refer to the description of the method embodiment.
  • the base station in this embodiment cooperates with the terminal device provided in the foregoing embodiment, and is based on a first type of signaling message between the MME and the terminal device and a second type of signaling message between the MME and the P-CSCF.
  • the data transmission does not need to specifically establish or restore the user plane RAB of the terminal device and the network air interface side, which saves network resources, improves the transmission efficiency of small data, reduces signaling interaction between the terminal device and the network side, and reduces network load.
  • FIG. 15 is a schematic structural diagram of an MME according to an embodiment of the present invention. As shown in FIG. 15, the MME of this embodiment includes: a third receiving module 151 and a third sending module 152.
  • the third receiving module 151 is configured to receive a first type of first signaling message sent by the base station, where the first type of the first signaling message is sent by the base station after receiving the RRC connection complete message sent by the terminal device
  • the RRC connection complete message is generated by the indication information in the RRC connection request message, where the RRC connection complete message includes the uplink data sent by the terminal device to the application server, where the first type of the first signaling message includes uplink data, where the indication information is used to indicate that the base station only Establish a signaling connection for the terminal device.
  • the third sending module 152 is connected to the third receiving module 151, and configured to send the uplink data received by the third receiving module 151 to the application server by using the first signaling message of the second type between the MME and the P-CSCF. .
  • the third receiving module 151 is further configured to: before receiving the first signaling message of the first type, receive an attach request message sent by the terminal device, and send the third sending module 152 to After the application server sends the first SIP registration request message, the first SIP registration returned by the application server after receiving the SIP identifier corresponding to the terminal device is completed by using the second type of the third signaling message between the MME and the P-CSCF.
  • the message, the attach request message includes an identifier of the terminal device.
  • the MME in this embodiment further includes: an obtaining module 153.
  • the obtaining module 153 is configured to obtain the SIP identifier corresponding to the terminal device according to the identifier of the terminal device, and generate a first SIP registration request message, where the first SIP registration request message includes the identifier of the terminal device and the SIP identifier corresponding to the terminal device.
  • the obtaining module 153 is configured to obtain, according to the identifier of the terminal device, a corresponding terminal device.
  • the SIP identifier includes: the obtaining module 153 is specifically configured to send a location update request message to the HSS, where the location update request message includes an identifier of the terminal device, and receives an identifier of the terminal device returned by the HSS according to the identifier of the terminal device, and a SIP identifier corresponding to the terminal device. The mapping relationship between them. Or
  • the obtaining module 153 is specifically configured to generate a SIP identifier corresponding to the terminal device according to the identifier of the terminal device.
  • the obtaining module 153 is connected to the third receiving module 151, and is configured to provide the third receiving module 151 with a SIP identifier corresponding to the terminal device.
  • the third sending module 152 is further configured to send a first SIP registration request message to the application server by using the second signaling message of the second type between the MME and the P-CSCF, and receive the first receiving module 151 by the third receiving module 151.
  • an attach accept message is sent to the terminal device, where the attach accept message includes a SIP registration completion message.
  • the MME of the embodiment implements the SIP registration process to the application server in the EPS attachment process of the terminal device through the third receiving module 151, the third sending module 152, and the obtaining module 153. There is only a signaling connection between the MME and the terminal device in this embodiment.
  • the third receiving module 151 is further configured to: before receiving the first signaling message of the first type, receive an attach request message sent by the terminal device, and send the third sending module 152 to After the terminal device sends the attach accept message, the receiving terminal device sends the first type of second signaling message according to the IP address allocated by the MME to the terminal device, and after the third sending module 152 sends the first SIP registration request message to the application server, And receiving, by the application server, a first SIP registration complete message returned after receiving the SIP identifier corresponding to the terminal device; the attach request message includes an identifier of the terminal device, where the second signaling message of the first type includes the first SIP registration request message The first SIP registration request message includes an identifier of the terminal device and a SIP identifier corresponding to the terminal device.
  • the MME in this embodiment further includes: an allocation module 154.
  • An allocation module 154 is configured to assign an IP address to the terminal device.
  • the third sending module 152 is further configured to receive the attach request at the third receiving module 151.
  • the connection accept message is sent to the terminal device, where the attach accept message includes the foregoing IP address
  • the third receiving module 151 receives the second signaling message of the first type, the third between the MME and the P-CSCF
  • the second type of the second signaling message is sent to the application server, and after receiving the first SIP registration complete message, the third receiving module 151 sends the first type of third signaling to the terminal device.
  • the message, the first type of third signaling message includes a first SIP registration complete message.
  • the allocating module 154 is connected to the third sending module 152, and configured to provide the third sending module 152 with an IP address allocated by the MME for the terminal device.
  • the MME of the present embodiment completes the EPS attach process of the terminal device through the third receiving module 151, the third sending module 152, and the allocating module 154, and causes the terminal device to complete the SIP registration process to the application server. There is only a signaling connection between the MME and the terminal device in this embodiment.
  • the third sending module 152 is further configured to: pass the second type between the MME and the P-CSCF before the third receiving module 151 receives the first signaling message of the first type. a second signaling message, sending a second SIP registration request message to the P-CSCF, so that the P-CSCF sends a second SIP registration request message to the application server, where the second type of second signaling message includes the second SIP And a registration request message, where the second SIP registration request message includes an identifier of the MME and a SIP identifier corresponding to the MME.
  • the third receiving module 151 is further configured to: after the third sending module 152 sends the second SIP registration request message, the receiving application server receives the MME corresponding to the third type of the third signaling message between the MME and the P-CSCF.
  • the second SIP registration completion message returned after the SIP identity.
  • the third receiving module 151 is further configured to: after receiving the second SIP registration complete message, receive an attach request message sent by the terminal device, where the attach request message includes an identifier of the terminal device.
  • the third sending module 152 is further configured to send an attach accept message to the terminal device after the third receiving module 151 receives the attach request message.
  • the MME of the embodiment completes the EPS attach process of the terminal device by using the third receiving module 151 and the third sending module 152, and completes the application to the application by using the third receiving module 151 and the third sending module 152 as user agents.
  • the SIP registration process of the server There is only a signaling connection between the MME and the terminal device in this embodiment.
  • the third receiving module 151 is further configured to send, by using the second type of the fourth signaling message between the MME and the P-CSCF, the receiving application server to send to the terminal.
  • the downlink data is prepared, and after the third sending module 152 sends the paging message to the terminal device, the service request message sent by the terminal device is received.
  • the third sending module 152 is further configured to: after the third receiving module 151 receives the downlink data, send the paging message to the terminal device, and after the third receiving module 151 receives the service request message, send the first type to the terminal device.
  • the fourth signaling message, the fourth type of the fourth signaling message includes downlink data.
  • the third sending module 152 is configured to send the uplink data to the application server by using the first type of the first signaling message between the MME and the P-CSCF, including:
  • the third sending module 152 is specifically configured to send a third type of first signaling message to the MSC server, where the third type of first signaling message includes uplink data, so that the MSC server encapsulates the uplink data in the second type.
  • a signaling message is sent to the P-CSCF to send the uplink data to the application server.
  • the third receiving module 151 is configured to receive the downlink data sent by the application server to the terminal device by using the fourth type of the fourth signaling message between the MME and the P-CSCF, where the third receiving module 151 is specifically configured to receive a third type of second signaling message sent by the MSC server, where the third type of the second signaling message is generated by the MSC server according to the second type of the fourth signaling message sent by the P-CSCF, the third type of The second signaling message includes downlink data.
  • the function modules of the MME provided in this embodiment may be used to perform the foregoing process of the data transmission method described in the MME.
  • the specific working principle is not described here. For details, refer to the description of the method embodiments.
  • the MME of this embodiment cooperates with the terminal device and the base station provided by the foregoing embodiment, based on the first type of signaling message between the MME and the terminal device, and the second type of signaling message between the MME and the P-CSCF.
  • the terminal device and the base station provided by the foregoing embodiment, based on the first type of signaling message between the MME and the terminal device, and the second type of signaling message between the MME and the P-CSCF.
  • FIG. 16 is a schematic structural diagram of an MME according to another embodiment of the present invention. As shown in FIG. 16, the MME of this embodiment includes: a receiver 161 and a transmitter 162.
  • the receiver 161 is configured to receive a first type of first signaling message sent by the base station, where the first type of the first signaling message is after the base station receives the RRC connection complete message sent by the terminal device, according to the And generating, by the terminal device, the indication information in the RRC connection request message, where the RRC connection complete message includes the uplink data sent by the terminal device to the application server, where the first type of the first signaling message includes the uplink data, where the indication information is used.
  • the base station is instructed to establish a signaling connection only for the terminal device.
  • the transmitter 162 is connected to the receiver 161, and configured to send the uplink data received by the receiver 161 to the application server by using the first signaling message of the second type between the MME and the P-CSCF.
  • the MME provided in this embodiment can be used to perform the foregoing data transmission method described in the MME.
  • the specific working principle is not described here. For details, refer to the description of the method embodiment.
  • the MME of this embodiment cooperates with the terminal device and the base station provided by the foregoing embodiment, based on the first type of signaling message between the MME and the terminal device, and the second type of signaling message between the MME and the P-CSCF.
  • the terminal device and the base station provided by the foregoing embodiment, based on the first type of signaling message between the MME and the terminal device, and the second type of signaling message between the MME and the P-CSCF.
  • FIG. 17 is a schematic structural diagram of a P-CSCF according to an embodiment of the present invention. As shown in FIG. 17, the P-CSCF of this embodiment includes: a fourth receiving module 171 and a fourth transmitting module 172.
  • the fourth receiving module 171 is configured to receive uplink data that is sent by the terminal device to the application server by using the first signaling message of the second type between the P-CSCF and the MME.
  • the first signaling message of the second type is the MME.
  • the second type of the first signaling message After receiving the first type of the first signaling message sent by the base station, the second type of the first signaling message includes the uplink data, and the uplink data is generated according to the uplink data in the first type of the first signaling message.
  • the amount of data is less than the preset data amount threshold.
  • the fourth sending module 172 is connected to the fourth receiving module 171, and configured to send the uplink data received by the fourth receiving module 171 to the S-CSCF, so that the S-CSCF sends the uplink data to the application server.
  • the fourth receiving module 171 is further configured to receive, by using the second type of the second signaling message between the P-CSCF and the MME, the second sending module, before receiving the uplink data.
  • a SIP registration request message and after the fourth sending module sends the first SIP registration request message to the application server, the first SIP registration completion message returned by the application server sent by the S-CSCF to receive the SIP identifier corresponding to the terminal device is received.
  • the first SIP registration request message includes an identifier of the terminal device and a SIP identifier corresponding to the terminal device.
  • the fourth sending module 172 is further configured to: after the fourth receiving module 171 receives the first SIP registration request message, send the first SIP registration request message to the S-CSCF, so that the S-CSCF sends the first SIP.
  • the registration request message is sent to the application server, and after the fourth receiving module 171 receives the first SIP registration completion message, the first SIP is sent to the MME through the second type of third signaling message between the P-CSCF and the MME. Registration completion message.
  • the fourth receiving module 171 is further configured to receive, by using the second type of the second signaling message between the P-CSCF and the MME, the second sending module, before receiving the uplink data.
  • a second SIP registration request message and after the fourth sending module 172 sends the second SIP registration request message to the S-CSCF, the second SIP registration returned by the application server sent by the S-CSCF after receiving the SIP identifier corresponding to the MME is received.
  • the completion message, the second SIP registration request message includes an identifier of the MME and a SIP identifier corresponding to the MME.
  • the fourth sending module 172 is further configured to: after the fourth receiving module 171 receives the second SIP registration request message, send the second SIP registration request message to the S-CSCF, so that the S-CSCF sends the second SIP registration request message. After the second SIP registration completion message is received by the application server, and after the fourth receiving module 171 receives the second SIP registration complete message, the second SIP registration complete message is sent to the MME by using the second type of third signaling message between the P-CSCF and the MME.
  • the fourth receiving module 171 is further configured to receive downlink data sent by the application server sent by the S-CSCF to the terminal device, and address information of the MME, where the address information of the MME is the S-CSCF according to the S-CSCF.
  • the SIP identifier corresponding to the terminal device is obtained by the HSS.
  • the HSS stores the mapping relationship between the identifier of the terminal device and the SIP identifier corresponding to the terminal device, and the mapping relationship between the identifier of the terminal device and the address information of the MME.
  • the fourth sending module 172 is further configured to: after the fourth receiving module 171 receives the downlink data and the address information of the MME, according to the address information of the MME, the second type of fourth signaling message between the P-CSCF and the MME is used. Send downlink data to the MME.
  • the fourth receiving module 171 is configured to: receive, by using the second signaling message between the P-CSCF and the MME, the uplink data that is sent by the terminal device to the application server, where the fourth receiving module is:
  • the 171 is specifically configured to receive the first signaling message of the second type sent by the MSC server, where the first signaling message of the second type is generated by the MSC server according to the first signaling message of the third type sent by the MME, where the third The first type of signaling message includes uplink data.
  • the fourth sending module 172 is configured to send downlink data to the MME by using a fourth type of fourth signaling message between the P-CSCF and the MME according to the address information of the MME. : The fourth sending module 172 is specifically configured to send the fourth type of the fourth signaling message to the MSC server, so that the MSC server encapsulates the downlink data in the fourth type of the fourth signaling message in the second type of the second type. The message is sent to the MME.
  • the functional modules of the P-CSCF provided in this embodiment can be used to execute the foregoing data transmission method described in the P-CSCF.
  • the specific working principle is not described here. For details, refer to the description of the method embodiments.
  • the P-CSCF in this embodiment cooperates with the terminal device, the base station, and the MME provided by the foregoing embodiment, based on the first type of signaling message between the MME and the terminal device, and the second type between the MME and the P-CSCF.
  • the signaling message carries out the transmission of small data, and does not need to specifically establish or restore the user plane RAB of the terminal device and the network air interface side, saves network resources, improves the transmission efficiency of small data, and reduces signaling interaction between the terminal device and the network side. Reduce network load.
  • FIG. 18 is a schematic structural diagram of a P-CSCF according to another embodiment of the present invention. As shown in FIG. 18, the P-CSCF of this embodiment includes: a receiver 181 and a transmitter 182.
  • the receiver 181 is configured to receive, by using a second type of first signaling message between the P-CSCF and the MME, uplink data that is sent by the terminal device to the application server, where the first signaling message of the second type is the MME.
  • the second type of the first signaling message After receiving the first type of the first signaling message sent by the base station, the second type of the first signaling message includes the uplink data, and the uplink data is generated according to the uplink data in the first type of the first signaling message.
  • the amount of data is less than the preset data amount threshold.
  • the transmitter 182 is connected to the receiver 181, and configured to send the uplink data received by the receiver 181 to the S-CSCF, so that the S-CSCF sends the uplink data to the application server.
  • the specific working principle of the method is not described here. For details, refer to the description of the method embodiment.
  • the P-CSCF in this embodiment cooperates with the terminal device, the base station, and the MME provided by the foregoing embodiment, based on the first type of signaling message between the MME and the terminal device, and the second type between the MME and the P-CSCF.
  • the signaling message carries out the transmission of small data, and does not need to specifically establish or restore the user plane RAB of the terminal device and the network air interface side, saves network resources, improves the transmission efficiency of small data, and reduces signaling interaction between the terminal device and the network side. Reduce network load.
  • An embodiment of the present invention provides a data transmission system, including: a terminal device, a base station, an MME, and a P-CSCF according to the foregoing embodiments of the present invention, where the P-CSCF is connected to the MME.
  • a terminal device including: a terminal device, a base station, an MME, and a P-CSCF according to the foregoing embodiments of the present invention, where the P-CSCF is connected to the MME.
  • the structure and working principle of the terminal device, the base station, the MME, and the P-CSCF are not described herein again. description of.
  • the data transmission system provided by this embodiment may be used to perform the process of the foregoing data transmission method embodiments, and may also be based on a first type of signaling message between the MME and the terminal device and a second type between the MME and the P-CSCF.
  • the signaling message carries out the transmission of small data, and does not need to specifically establish or restore the user plane RAB of the terminal device and the air interface side of the network, saves network resources, improves the transmission efficiency of small data, and reduces signaling interaction between the terminal device and the network side. Reduce network load.
  • the method includes the steps of the foregoing method embodiments; and the foregoing storage medium includes: a medium that can store program codes, such as a ROM, a RAM, a magnetic disk, or an optical disk.

Abstract

本发明实施例提供一种数据传输方法、设备及系统。一种方法包括:终端设备判断待发送的上行数据是否小于预设数据量门限;如果小于,与基站建立RRC连接,将上行数据携带在RRC连接完成消息中发送给基站,以使基站将上行数据通过其与MME之间的信令消息发送给MME,进而使MME通过其与P-CSCF之间的信令消息将上行数据发送给对应的应用服务器。本发明技术方案通过信令消息传输小数据,解决了网络资源。

Description

数据传输方法、 设备及系统 技术领域 本发明涉及通信技术, 尤其涉及一种数据传输方法、 设备及系统。 背景技术
机器型通信 ( Machine Type Communication, 简称为 MTC )是指一个或 多个网元或设备之间在不需要人为参与的情况下进行的网络通信, 也可以称 之为机器对机器(Machine to Machine, 简称为 M2M )通信。 MTC以及一些 类似 MTC的其他通信具有交互流量小, 且交互突发等特点, 因此, MTC及 类似 MTC的其他通信过程中的数据传输常被称为小数据传输(英文为 Small Data Transmissions )或氐数据流量(英文为 Low Data Usage )传输, 相应的, 与人对人( Human to Human, 简称为 H2H )终端相比, MTC终端及类似 MTC 终端的终端常被称为小数据传输终端或低数据流量终端。
目前,各种小数据传输都是小数据传输架构与移动通信网络结合实现的。 以 MTC中的小数据传输为例, MTC架构主要包括 MTC-交互功能(Machine Type Communication-Interworking Function, 简称为 MTC-IWF )网元和业务能 力服务器( Services Capability Server,简称为 SCS )。 MTC-IWF主要实现 SCS 鉴权、 外部标识映射、 查询移动通信网络中的归属用户服务器 (Home Subscriber Server, 简称为 HSS )获得服务节点信息等功能; SCS提供 MTC 应用的能力 , 例如 M2M终端触发等业务能力 , 而 MTC应用由 MTC架构之 外的应用服务器(Application Server, 简称为 AS )提供。 为了保障小数据传 输, 现有方案需要移动通信网络中的网元, 例如分组数据网关(Packet Data Network Gateway, 简称为 PGW )等, 为每个小数据传输终端分配互联网协 议(Internet Protocol, 简称为 IP )地址, 创建数据传输相应的无线接入承载 ( Radio Access Bear, 简称为 RAB ) , 并预留进行数据传输所需的资源, 这 会造成移动通信网络中资源的浪费。 发明内容 本发明实施例提供一种数据传输方法、 设备及系统, 用以减少小数据传 输消耗的网络资源。
本发明实施例第一方面提供一种数据传输方法, 包括:
终端设备判断待发送上行数据的数据量是否小于预设数据量门限; 当所述上行数据的数据量小于所述预设数据量门限时, 所述终端设备向 基站发送无线资源控制 RRC连接请求消息, 所述 RRC连接请求消息包括指 示所述基站仅为所述终端设备建立信令连接的指示信息;
所述终端设备接收所述基站发送的 RRC连接建立消息;
所述终端设备将所述上行数据携带在 RRC 连接完成消息中发送给所述 基站, 以使所述基站根据所述指示信息, 将所述上行数据通过所述基站与移 动性管理实体 MME之间的第一类型的第一信令消息发送给所述 MME,以使 所述 MME通过所述 MME与代理呼叫会话控制功能 P-CSCF之间的第二类型 在一方面的第一种可能的实现方式中, 所述终端设备判断待发送上行数 据的数据量是否小于预设数据量门限之前包括:
所述终端设备向所述 MME发送附着请求消息, 以使所述 MME通过所 述 MME与所述 P-CSCF之间的第二类型的第二信令消息向所述应用服务器 发送第一会话初始协议 SIP注册请求消息, 所述附着请求消息包括所述终端 设备的标识, 所述第一 SIP注册请求消息包括所述终端设备的标识和所述终 端设备对应的 SIP标识;
所述终端设备接收所述 MME发送的附着接受消息, 所述附着接受消息 是所述 MME通过所述 MME与所述 P-CSCF之间的第二类型的第三信令消息 接收到所述应用服务器返回的第一 SIP注册完成消息后生成的,所述第一 SIP 注册完成消息是所述应用服务器在接收到所述终端设备对应的 SIP标识后返 回的;
其中, 所述终端设备与所述 MME之间仅存在信令连接。
在第一方面的第二种可能的实现方式中, 所述终端设备判断待发送上行 数据的数据量是否小于预设数据量门限之前包括:
所述终端设备向所述 MME发送附着请求消息, 所述附着请求消息包括 所述终端设备的标识; 所述终端设备接收所述 MME发送的附着接受消息, 所述附着接受消息 包括所述 MME为所述终端设备分配的 IP地址;
所述终端设备根据所述 IP地址, 通过所述终端设备与所述 MME之间的 第一类型的第二信令消息向所述 MME发送第一 SIP注册请求消息, 以使所 述 MME通过所述 MME与所述 P-CSCF之间的第二类型的第二信令消息,将 所述第一 SIP注册请求消息发送给所述应用服务器, 所述第一 SIP注册请求 消息包括所述终端设备的标识和所述终端设备对应的 SIP标识;
所述终端设备通过所述终端设备与所述 MME之间的第一类型的第三信 令消息, 接收所述 MME返回的第一 SIP注册完成消息, 所述第一 SIP注册 完成消息是所述应用服务器在接收到所述终端设备对应的 SIP标识后返回的, 所述 MME是通过所述 MME与所述 P-CSCF之间的第二类型的第三信令消息 接收到所述第一 SIP注册完成消息的;
其中, 所述终端设备与所述 MME之间仅存在信令连接。
在第一方面的第三种可能的实现方式中, 所述终端设备判断待发送上行 数据的数据量是否小于预设数据量门限之前包括:
所述终端设备向所述 MME发送附着请求消息, 所述附着请求消息包括 所述终端设备的标识;
所述终端设备接收所述 MME发送的附着接受消息;
其中, 所述终端设备与所述 MME之间仅存在信令连接。
结合第一方面或第一方面的第一种可能的实现方式或第一方面的第二种 可能的实现方式或第一方面的第三种可能的实现方式, 在第一方面的第四种 可能的实现方式中, 所述数据传输方法还包括:
所述终端设备接收所述 MME发送的寻呼消息, 所述寻呼消息是所述 MME通过所述 MME与所述 P-CSCF之间的第二类型的第四信令消息在接收 到所述应用服务器发送给所述终端设备的下行数据后生成的;
所述终端设备根据所述寻呼消息, 向所述 MME发送服务请求消息, 所 述服务请求消息用于指示所述 MME仅为所述终端设备建立信令连接;
所述终端设备接收所述 MME根据所述服务请求消息发送的第一类型的 第四信令消息, 所述第一类型的第四信令消息包括所述下行数据。
本发明实施例第二方面提供一种数据传输方法, 包括: 基站接收终端设备发送的无线资源控制 RRC连接请求消息, 所述 RRC 连接请求消息是所述终端设备判断出待发送上行数据的数据量小于预设数据 量门限时生成的,所述 RRC连接请求消息包括指示所述基站仅为所述终端设 备建立信令连接的指示信息;
所述基站向所述终端设备发送 RRC连接建立消息;
所述基站接收所述终端设备发送的 RRC连接完成消息, 所述 RRC连接 完成消息包括所述上行数据;
所述基站根据所述指示信息, 通过所述基站与移动性管理实体 MME之 间的第一类型的第一信令消息将所述上行数据发送给所述 MME, 以使所述 MME通过所述 MME与代理呼叫会话控制功能 P-CSCF之间的第二类型的第 本发明实施例第三方面提供一种数据传输方法, 包括:
移动性管理实体 MME接收基站发送的第一类型的第一信令消息, 所述 第一类型的第一信令消息是所述基站在接收到终端设备发送的无线资源控制 RRC连接完成消息后, 根据所述终端设备发送的 RRC连接请求消息中的指 示信息生成的,所述 RRC连接完成消息包括所述终端设备发送给应用服务器 的上行数据, 所述第一类型的第一信令消息包括所述上行数据, 所述指示信 息用于指示所述基站仅为所述终端设备建立信令连接;
所述 MME通过所述 MME与代理呼叫会话控制功能 P-CSCF之间的第二 类型的第一信令消息, 将所述上行数据发送给所述应用服务器。
在第三方面的第一种可能的实现方式中, 所述移动性管理实体 MME接 收基站发送的第一类型的第一信令消息之前包括:
所述 MME接收所述终端设备发送的附着请求消息, 所述附着请求消息 包括所述终端设备的标识;
所述 MME根据所述终端设备的标识, 获取所述终端设备对应的会话初 始协议 SIP标识, 并生成第一 SIP注册请求消息, 所述第一 SIP注册请求消 息包括所述终端设备的标识和所述终端设备对应的 SIP标识;
所述 MME通过所述 MME与所述 P-CSCF之间的第二类型的第二信令消 息向所述应用服务器发送所述第一 SIP注册请求消息;
所述 MME通过所述 MME与所述 P-CSCF之间的第二类型的第三信令消 息, 接收所述应用服务器在接收到所述终端设备对应的 SIP标识后返回的第 一 SIP注册完成消息;
所述 MME向所述终端设备发送附着接受消息, 所述附着接受消息包括 所述第一 SIP注册完成消息;
其中, 所述终端设备与所述 MME之间仅存在信令连接。
结合第三方面的第一种可能的实现方式, 在第三方面的第二种可能的实 现方式中, 所述 MME根据所述终端设备的标识, 获取所述终端设备对应的 SIP标识包括:
所述 MME向位置归属服务器 HSS发送位置更新请求消息, 所述位置更 新请求消息包括所述终端设备的标识;
所述 MME接收所述 HSS根据所述终端设备的标识返回的所述终端设备 的标识和所述终端设备对应的 SIP标识之间的映射关系; 或者
所述 MME根据所述终端设备的标识, 生成所述终端设备对应的 SIP标 识。
在第三方面的第三种可能的实现方式中, 所述移动性管理实体 MME接 收基站发送的第一类型的第一信令消息之前包括:
所述 MME接收所述终端设备发送的附着请求消息, 所述附着请求消息 包括所述终端设备的标识;
所述 MME为所述终端设备分配 IP地址;
所述 MME向所述终端设备发送附着接受消息, 所述附着接受消息包括 所述 IP地址;
所述 MME接收所述终端设备根据所述 IP地址发送的第一类型的第二信 令消息, 所述第一类型的第二信令消息包括第一 SIP注册请求消息, 所述第 一 SIP注册请求消息包括所述终端设备的标识和所述终端设备对应的 SIP标 识;
所述 MME通过所述 MME与所述 P-CSCF之间的第二类型的第二信令消 息, 将所述第一 SIP注册请求消息发送给所述应用服务器;
所述 MME通过所述 MME与所述 P-CSCF之间的第二类型的第三信令消 息, 接收所述应用服务器在接收到所述终端设备对应的 SIP标识返回的第一 SIP注册完成消息; 所述 MME向所述终端设备发送第一类型的第三信令消息, 所述第一类 型的第三信令消息包括所述第一 SIP注册完成消息;
其中, 所述终端设备与所述 MME之间仅存在信令连接。
在第三方面的第四种可能的实现方式中, 所述移动性管理实体 MME接 收基站发送的第一类型的第一信令消息之前包括:
所述 MME通过所述 MME与所述 P-CSCF之间的第二类型的第二信令消 息, 向所述 P-CSCF发送第二 SIP注册请求消息, 以使所述 P-CSCF将所述第 二 SIP注册请求消息发送给所述应用服务器, 所述第二类型的第二信令消息 包括所述第二 SIP注册请求消息,所述第二 SIP注册请求消息包括所述 MME 的标识和所述 MME对应的 SIP标识;
所述 MME通过所述 MME与所述 P-CSCF之间的第二类型的第三信令消 息, 接收所述应用服务器在接收到所述 MME对应的 SIP标识后返回的第二 SIP注册完成消息。
结合第三方面的第四种可能的实现方式, 在第三方面的第五种可能的实 现方式中,所述 MME通过所述 MME与所述 P-CSCF之间的第二类型的第三 信令消息, 接收所述应用服务器在接收到所述 MME对应的 SIP标识后返回 的第二 SIP注册完成消息之后包括:
所述 MME接收所述终端设备发送的附着请求消息, 所述附着请求消息 包括所述终端设备的标识;
所述 MME向所述终端设备发送附着接受消息;
其中, 所述终端设备与所述 MME之间仅存在信令连接。
结合第三方面或第三方面的第一种可能的实现方式或第三方面的第二种 可能的实现方式或第三方面的第三种可能的实现方式或第三方面的第四种可 能的实现方式或第三方面的第五种可能的实现方式, 在第三方面的第六种可 能的实现方式中, 所述的数据传输方法还包括:
所述 MME通过所述 MME与所述 P-CSCF之间的第二类型的第四信令消 息, 接收所述应用服务器发送给所述终端设备的下行数据;
所述 MME向所述终端设备发送寻呼消息;
所述 MME接收所述终端设备发送的服务请求消息;
所述 MME向所述终端设备发送第一类型的第四信令消息, 所述第一类 型的第四信令消息包括所述下行数据。
结合第三方面或第三方面的第一种可能的实现方式或第三方面的第二种 可能的实现方式或第三方面的第三种可能的实现方式或第三方面的第四种可 能的实现方式或第三方面的第五种可能的实现方式, 在第三方面的第七种可 能的实现方式中, 所述 MME 通过所述 MME 与代理呼叫会话控制功能 P-CSCF之间的第二类型的第一信令消息,将所述上行数据发送给所述应用服 务器包括:
所述 MME向 MSC服务器发送第三类型的第一信令消息,所述第三类型 的第一信令消息包括所述上行数据,以使所述 MSC服务器将所述上行数据封 装在所述第二类型的第一信令消息中发送给所述 P-CSCF,以将所述上行数据 发送给所述应用服务器。
结合第三方面的第六种可能的实现方式, 在第三方面的第八种可能的实 现方式中,所述 MME通过所述 MME与所述 P-CSCF之间的第二类型的第四 信令消息, 接收所述应用服务器发送给所述终端设备的下行数据包括:
所述 MME接收 MSC服务器发送的第三类型的第二信令消息,所述第三 类型的第二信令消息是所述 MSC服务器根据所述 P-CSCF发送的所述第二类 型的第四信令消息生成的,所述第三类型的第二信令消息包括所述下行数据。
本发明实施例第四方面提供一种数据传输方法, 包括:
代理呼叫会话控制功能 P-CSCF 通过所述 P-CSCF 与移动性管理实体 MME之间的第二类型的第一信令消息,接收终端设备发送给应用服务器的上 行数据; 所述第二类型的第一信令消息是所述 MME接收到基站发送的第一 类型的第一信令消息后, 根据所述第一类型的第一信令消息中的所述上行数 据生成的, 所述第二类型的第一信令消息包括所述上行数据, 所述上行数据 的数据量小于预设数据量门限;
所述 P-CSCF将所述上行数据发送给 S-CSCF, 以使所述 S-CSCF将所述 上行数据发送给所述应用服务器。
在第四方面的第一种可能的实现方式中, 所述代理呼叫会话控制功能 P-CSCF通过所述 P-CSCF与移动性管理实体 MME之间的第二类型的第一信 令消息, 接收终端设备发送给应用服务器的上行数据之前包括:
所述 P-CSCF通过所述 P-CSCF与所述 MME之间的第二类型的第二信令 消息, 接收所述 MME发送的第一 SIP注册请求消息, 所述第一 SIP注册请 求消息包括所述终端设备的标识和所述终端设备对应的 SIP标识;
所述 P-CSCF将所述第一 SIP注册请求消息发送给所述 S-CSCF, 以使所 述 S-CSCF将所述第一 SIP注册请求消息发送给所述应用服务器;
所述 P-CSCF接收所述 S-CSCF发送的所述应用服务器在接收到所述终端 设备对应的 SIP标识返回的第一 SIP注册完成消息;
所述 P-CSCF通过所述 P-CSCF与所述 MME之间的第二类型的第三信令 消息, 向所述 MME发送所述第一 SIP注册完成消息。
在第四方面的第二种可能的实现方式中, 所述代理呼叫会话控制功能 P-CSCF通过所述 P-CSCF与移动性管理实体 MME之间的第二类型的第一信 令消息, 接收终端设备发送给应用服务器的上行数据之前包括:
所述 P-CSCF通过所述 P-CSCF与所述 MME之间的第二类型的第二信令 消息, 接收所述 MME发送的第二 SIP注册请求消息, 所述第二 SIP注册请 求消息包括所述 MME的标识和所述 MME对应的 SIP标识;
所述 P-CSCF将所述第二 SIP注册请求消息发送给所述 S-CSCF, 以使所 述 S-CSCF将所述第二 SIP注册请求消息发送给所述应用服务器;
所述 P-CSCF接收所述 S-CSCF 发送的所述应用服务器在接收到所述 MME对应的 SIP标识后返回的第二 SIP注册完成消息;
所述 P-CSCF通过所述 P-CSCF与所述 MME之间的第二类型的第三信令 消息, 向所述 MME发送所述第二 SIP注册完成消息。
结合第四方面的第二种可能的实现方式, 在第四方面的第三种可能的实 现方式中, 所述数据传输方法还包括:
所述 P-CSCF接收所述 S-CSCF发送的所述应用服务器发送给终端设备的 下行数据和所述 MME的地址信息,所述 MME的地址信息是所述 S-CSCF根 据所述终端设备对应的 SIP标识查询归属存储服务器 HSS获取的, 所述 HSS 存储有所述终端设备的标识与所述终端设备对应的 SIP标识之间的映射关系, 以及所述终端设备的标识与所述 MME的地址信息之间的映射关系;
所述 P-CSCF根据所述 MME的地址信息 ,通过所述 P-CSCF与所述 MME 之间的第二类型的第四信令消息, 向所述 MME发送所述下行数据。
结合第四方面或第四方面的第一种可能的实现方式或第四方面的第二种 可能的实现方式或第四方面的第三种可能的实现方式, 在第四方面的第四种 可能的实现方式中, 所述代理呼叫会话控制功能 P-CSCF 通过所述 P-CSCF 与移动性管理实体 MME之间的第二类型的第一信令消息, 接收终端设备发 送给应用服务器的上行数据包括:
所述 P-CSCF接收 MSC服务器发送的所述第二信令消息,所述第二信令 消息是所述 MSC服务器根据所述 MME发送的第三类型的第一信令消息生成 的, 所述第三类型的第一信令消息包括所述上行数据。
结合第四方面的第四种可能的实现方式, 在第四方面的第五种可能的实 现方式中, 所述 P-CSCF根据所述 MME的地址信息, 通过所述 P-CSCF与所 述 MME之间的第二类型的第四信令消息, 向所述 MME发送所述下行数据 包括:
所述 P-CSCF向 MSC服务器发送的所述第二类型的第四信令消息, 以使 所述 MSC服务器将所述第二类型的第四信令消息中的所述下行数据封装在 第三类型的第二信令消息中发送给所述 MME。
本发明实施例第五方面提供一种终端设备, 包括:
判断模块,用于判断待发送上行数据的数据量是否小于预设数据量门限; 第一发送模块, 用于在所述判断模块判断出所述上行数据的数据量小于 所述预设数据量门限时, 向基站发送无线资源控制 RRC连接请求消息, 所述 RRC连接请求消息包括指示所述基站仅为所述终端设备建立信令连接的指示 信息;
第一接收模块,用于在所述第一发送模块发送所述 RRC连接请求消息之 后, 接收所述基站发送的 RRC连接建立消息;
所述第一发送模块还用于在所述第一接收模块接收到所述 RRC 连接建 立消息后, 将所述上行数据携带在 RRC连接完成消息中发送给所述基站, 以 使所述基站根据所述指示信息, 将所述上行数据通过所述基站与移动性管理 实体 MME之间的第一类型的第一信令消息发送给所述 MME ,以使所述 MME 通过所述 MME与代理呼叫会话控制功能 P-CSCF之间的第二类型的第一信 在第五方面的第一种可能的实现方式中, 所述第一发送模块还用于在所 述判断模块判断待发送上行数据的数据量是否小于预设数据量门限之前, 向 所述 MME发送附着请求消息,以使所述 MME通过所述 MME与所述 P-CSCF 之间的第二类型的第二信令消息向所述应用服务器发送第一会话初始协议 SIP 注册请求消息, 所述附着请求消息包括所述终端设备的标识, 所述第一 SIP注册请求消息包括所述终端设备的标识和所述终端设备对应的 SIP标识; 所述第一接收模块还用于在所述第一发送模块向所述 MME发送所述附 着请求消息后, 接收所述 MME发送的附着接受消息, 所述附着接受消息是 所述 MME通过所述 MME与所述 P-CSCF之间的第二类型的第三信令消息接 收到所述应用服务器返回的第一 SIP注册完成消息后生成的, 所述第一 SIP 注册完成消息是所述应用服务器在接收到所述终端设备对应的 SIP标识后返 回的;
其中, 所述终端设备与所述 MME之间仅存在信令连接。
在第五方面的第二种可能的实现方式中, 所述第一发送模块还用于在所 述判断模块判断待发送上行数据的数据量是否小于预设数据量门限之前, 向 所述 MME发送附着请求消息, 所述附着请求消息包括所述终端设备的标识; 以及用于在所述第一接收模块接收到所述 MME发送的附着接受消息后, 根 据所述附着接受消息中所述 MME为所述终端设备分配的 IP地址, 通过所述 终端设备与所述 MME之间的第一类型的第二信令消息向所述 MME发送第 一 SIP注册请求消息 ,以使所述 MME通过所述 MME与所述 P-CSCF之间的 第二类型的第二信令消息, 将所述第一 SIP注册请求消息发送给所述应用服 务器, 所述第一 SIP注册请求消息包括所述终端设备的标识和所述终端设备 对应的 SIP标识;
所述第一接收模块还用于在所述第一发送模块向所述 MME发送所述附 着请求消息后, 接收所述 MME发送的所述附着接受消息, 所述附着接受消 息包括所述 MME为所述终端设备分配的 IP地址; 以及用于在所述第一发送 模块向所述 MME发送所述第一 SIP注册请求消息之后, 通过所述终端设备 与所述 MME之间的第一类型的第三信令消息, 接收所述 MME返回的第一 SIP注册完成消息,所述第一 SIP注册完成消息是所述应用服务器在接收到所 述终端设备对应的 SIP标识后返回的, 所述 MME是通过所述 MME与所述 P-CSCF之间的第二类型的第三信令消息接收到所述第一 SIP 注册完成消息 的; 其中, 所述终端设备与所述 MME之间仅存在信令连接。
在第五方面的第三种可能的实现方式中, 所述第一发送模块还用于在所 述判断模块判断待发送上行数据的数据量是否小于预设数据量门限之前, 向 所述 MME发送附着请求消息, 所述附着请求消息包括所述终端设备的标识; 所述第一接收模块还用于在所述第一发送模块向所述 MME发送所述附 着请求消息后, 接收所述 MME发送的附着接受消息;
其中, 所述终端设备与所述 MME之间仅存在信令连接。
结合第五方面或第五方面的第一种可能的实现方式或第五方面的第二种 可能的实现方式或第五方面的第三种可能的实现方式, 在第五方面的第四种 可能的实现方式中, 所述第一接收模块还用于接收所述 MME发送的寻呼消 息, 以及接收所述 MME根据所述第一发送模块发送的服务请求消息发送的 第一类型的第四信令消息, 所述寻呼消息是所述 MME通过所述 MME与所 述 P-CSCF之间的第二类型的第四信令消息接收到所述应用服务器发送给所 述终端设备的下行数据后生成的, 所述第一类型的第四信令消息包括所述下 行数据;
所述第一发送模块还用于在所述第一接收模块接收到所述寻呼消息后, 向所述 MME发送服务请求消息, 所述服务请求消息用于指示所述 MME仅 为所述终端设备建立信令连接。
本发明实施例第六方面提供一种终端设备, 包括:
处理器, 用于判断待发送上行数据的数据量是否小于预设数据量门限; 发送器, 用于在所述处理器判断出所述上行数据的数据量小于所述预设 数据量门限时, 向基站发送无线资源控制 RRC连接请求消息, 所述 RRC连 接请求消息包括指示所述基站仅为所述终端设备建立信令连接的指示信息; 接收器, 用于在所述发送器发送所述 RRC连接请求消息之后, 接收所述 基站发送的 RRC连接建立消息;
所述发送器还用于在所述接收器接收到所述 RRC连接建立消息后 ,将所 述上行数据携带在 RRC连接完成消息中发送给所述基站,以使所述基站根据 所述指示信息, 将所述上行数据通过所述基站与移动性管理实体 MME之间 的第一类型的第一信令消息发送给所述 MME ,以使所述 MME通过所述 MME 与代理呼叫会话控制功能 P-CSCF之间的第二类型的第一信令消息将所述上 行数据发送给所述上行数据对应的应用服务器。
本发明实施例第七方面提供一种基站, 包括:
第二接收模块,用于接收终端设备发送的无线资源控制 RRC连接请求消 息, 以及在第二发送模块向所述终端设备发送 RRC连接建立消息后, 接收所 述终端设备发送的 RRC连接完成消息, 所述 RRC连接请求消息是所述终端 设备判断出待发送上行数据的数据量小于预设数据量门限时生成的, 所述 RRC连接请求消息包括指示所述基站仅为所述终端设备建立信令连接的指示 信息, 所述 RRC连接完成消息包括所述上行数据;
所述第二发送模块,用于在所述第二接收模块接收到所述 RRC连接请求 消息后, 向所述终端设备发送所述 RRC连接建立消息, 以及在所述第二接收 模块接收到所述 RRC连接完成消息后, 根据所述指示信息, 通过所述基站与 移动性管理实体 MME之间的第一类型的第一信令消息将所述上行数据发送 给所述 MME, 以使所述 MME 通过所述 MME 与代理呼叫会话控制功能 P-CSCF之间的第二类型的第一信令消息将所述上行数据发送给所述上行数 据对应的应用服务器。
本发明实施例第八方面提供一种基站, 包括: 接收器和发送器; 所述接收器, 用于接收终端设备发送的无线资源控制 RRC 连接请求消 息, 以及在所述发送器向所述终端设备发送 RRC连接建立消息后,接收所述 终端设备发送的 RRC连接完成消息, 所述 RRC连接请求消息是所述终端设 备判断出待发送上行数据的数据量小于预设数据量门限时生成的, 所述 RRC 连接请求消息包括指示所述基站仅为所述终端设备建立信令连接的指示信 息, 所述 RRC连接完成消息包括所述上行数据;
所述发送器, 用于在所述接收器接收到所述 RRC连接请求消息后, 向所 述终端设备发送所述 RRC连接建立消息,以及在所述接收器接收到所述 RRC 连接完成消息后,根据所述指示信息,通过所述基站与移动性管理实体 MME 之间的第一类型的第一信令消息将所述上行数据发送给所述 MME,以使所述 MME通过所述 MME与代理呼叫会话控制功能 P-CSCF之间的第二类型的第 本发明实施例第九方面提供一种移动性管理实体 MME, 包括: 第三接收模块, 用于接收基站发送的第一类型的第一信令消息, 所述第 一类型的第一信令消息是所述基站在接收到终端设备发送的无线资源控制
RRC连接完成消息后, 根据所述终端设备发送的 RRC连接请求消息中的指 示信息生成的,所述 RRC连接完成消息包括所述终端设备发送给应用服务器 的上行数据, 所述第一类型的第一信令消息包括所述上行数据, 所述指示信 息用于指示所述基站仅为所述终端设备建立信令连接;
第三发送模块, 用于通过所述 MME 与代理呼叫会话控制功能 P-CSCF 之间的第二类型的第一信令消息, 将所述上行数据发送给所述应用服务器。
在第九方面的第一种可能的实现方式中, 所述第三接收模块还用于在接 收所述第一类型的第一信令消息之前, 接收所述终端设备发送的附着请求消 息, 以及在所述第三发送模块向所述应用服务器发送第一 SIP注册请求消息 后, 通过所述 MME与所述 P-CSCF之间的第二类型的第三信令消息, 接收 所述应用服务器在接收到所述终端设备对应的 SIP标识后返回的第一 SIP注 册完成消息, 所述附着请求消息包括所述终端设备的标识;
所述 MME还包括:
获取模块, 用于根据所述终端设备的标识, 获取所述终端设备对应的会 话初始协议 SIP标识, 并生成所述第一 SIP注册请求消息, 所述第一 SIP注 册请求消息包括所述终端设备的标识和所述终端设备对应的 SIP标识;
所述第三发送模块还用于通过所述 MME与所述 P-CSCF之间的第二类 型的第二信令消息向所述应用服务器发送所述第一 SIP注册请求消息, 以及 在所述第三接收模块接收到所述第一 SIP注册完成消息后, 向所述终端设备 发送附着接受消息, 所述附着接受消息包括所述第一 SIP注册完成消息; 其中, 所述终端设备与所述 MME之间仅存在信令连接。
结合第九方面的第一种可能的实现方式, 在第九方面的第二种可能的实 现方式中, 所述获取模块用于根据所述终端设备的标识, 获取所述终端设备 对应的 SIP标识包括:
所述获取模块具体用于向位置归属服务器 HSS发送位置更新请求消息, 所述位置更新请求消息包括所述终端设备的标识, 并接收所述 HSS根据所述 终端设备的标识返回的所述终端设备的标识和所述终端设备对应的 SIP标识 之间的映射关系; 或者
所述获取模块具体用于根据所述终端设备的标识, 生成所述终端设备对 应的 SIP标识。
在第九方面的第三种可能的实现方式中, 所述第三接收模块还用于在接 收所述第一类型的第一信令消息之前, 接收所述终端设备发送的附着请求消 息, 以及在所述第三发送模块向所述终端设备发送附着接受消息后, 接收所 第二信令消息, 并在所述第三发送模块向所述应用服务器发送第一 SIP注册 请求消息后, 接收所述应用服务器在接收到所述终端设备对应的 SIP标识后 返回的第一 SIP注册完成消息; 所述附着请求消息包括所述终端设备的标识, 所述第一类型的第二信令消息包括所述第一 SIP注册请求消息,所述第一 SIP 注册请求消息包括所述终端设备的标识和所述终端设备对应的 SIP标识; 所述 MME还包括: 分配模块, 用于为所述终端设备分配所述 IP地址; 所述第三发送模块还用于在所述第三接收模块接收到所述附着请求消息 后, 向所述终端设备发送所述附着接受消息, 所述附着接受消息包括所述 IP 地址, 以及在所述第三接收模块接收到所述第一类型的第二信令消息后, 通 过所述 MME与所述 P-CSCF之间的第二类型的第二信令消息, 将所述第一 SIP注册请求消息发送给所述应用服务器,以及在所述第三接收模块接收到所 述第一 SIP注册完成消息后, 向所述终端设备发送第一类型的第三信令消息, 所述第一类型的第三信令消息包括所述第一 SIP注册完成消息;
其中, 所述终端设备与所述 MME之间仅存在信令连接。
在第九方面的第四种可能的实现方式中, 所述第三发送模块还用于在所 述第三接收模块接收所述第一类型的第一信令消息之前, 通过所述 MME与 所述 P-CSCF之间的第二类型的第二信令消息, 向所述 P-CSCF发送第二 SIP 注册请求消息, 以使所述 P-CSCF将所述第二 SIP注册请求消息发送给所述 应用服务器,所述第二类型的第二信令消息包括所述第二 SIP注册请求消息, 所述第二 SIP注册请求消息包括所述 MME的标识和所述 MME对应的 SIP 标识;
所述第三接收模块还用于在所述第三发送模块发送所述第二 SIP注册请 求消息后, 通过所述 MME与所述 P-CSCF之间的第二类型的第三信令消息, 接收所述应用服务器在接收到所述 MME对应的 SIP标识后返回的第二 SIP 注册完成消息。 结合第九方面的第四种可能的实现方式, 在第九方面的第五种可能的实 现方式中,所述第三接收模块还用于在接收到所述第二 SIP注册完成消息后, 接收所述终端设备发送的附着请求消息, 所述附着请求消息包括所述终端设 备的标识;
所述第三发送模块还用于在所述第三接收模块接收到所述附着请求消息 后, 向所述终端设备发送附着接受消息;
其中, 所述终端设备与所述 MME之间仅存在信令连接。
结合第九方面或第九方面的第一种可能的实现方式或第九方面的第二种 可能的实现方式或第九方面的第三种可能的实现方式或第九方面的第四种可 能的实现方式或第九方面的第五种可能的实现方式, 在第九方面的第六种可 能的实现方式中, 所述第三接收模块还用于通过所述 MME 与所述 P-CSCF 之间的第二类型的第四信令消息, 接收所述应用服务器发送给所述终端设备 的下行数据, 以及在所述第三发送模块向所述终端设备发送寻呼消息后, 接 收所述终端设备发送的服务请求消息;
所述第三发送模块还用于在所述第三接收模块接收到所述下行数据后, 向所述终端设备发送所述寻呼消息, 以及在所述第三接收模块接收到所述服 务请求消息后, 向所述终端设备发送第一类型的第四信令消息, 所述第一类 型的第四信令消息包括所述下行数据。
结合第九方面或第九方面的第一种可能的实现方式或第九方面的第二种 可能的实现方式或第九方面的第三种可能的实现方式或第九方面的第四种可 能的实现方式或第九方面的第五种可能的实现方式, 在第九方面的第七种可 能的实现方式中, 所述第三发送模块用于通过所述 MME与代理呼叫会话控 制功能 P-CSCF之间的第二类型的第一信令消息, 将所述上行数据发送给所 述应用服务器包括:
所述第三发送模块具体用于向 MSC 服务器发送第三类型的第一信令消 息, 所述第三类型的第一信令消息包括所述上行数据, 以使所述 MSC服务器 将所述上行数据封装在所述第二类型的第一信令消息中发送给所述 P-CSCF, 以将所述上行数据发送给所述应用服务器。
结合第九方面的第六种可能的实现方式, 在第九方面的第八种可能的实 现方式中, 所述第三接收模块用于通过所述 MME与所述 P-CSCF之间的第 二类型的第四信令消息, 接收所述应用服务器发送给所述终端设备的下行数 据包括:
所述第三接收模块具体用于接收 MSC服务器发送的第三类型的第二信 令消息, 所述第三类型的第二信令消息是所述 MSC服务器根据所述 P-CSCF 发送的所述第二类型的第四信令消息生成的, 所述第三类型的第二信令消息 包括所述下行数据。
本发明实施例第十方面提供一种移动性管理实体, 包括:
接收器, 用于接收基站发送的第一类型的第一信令消息, 所述第一类型 的第一信令消息是所述基站在接收到终端设备发送的无线资源控制 RRC 连 接完成消息后,根据所述终端设备发送的 RRC连接请求消息中的指示信息生 成的,所述 RRC连接完成消息包括所述终端设备发送给应用服务器的上行数 据, 所述第一类型的第一信令消息包括所述上行数据, 所述指示信息用于指 示所述基站仅为所述终端设备建立信令连接;
发送器, 用于通过所述 MME与代理呼叫会话控制功能 P-CSCF之间的 第二类型的第一信令消息, 将所述上行数据发送给所述应用服务器。
本发明实施例第十一方面提供一种代理呼叫会话控制功能 P-CSCF, 包 括:
第四接收模块, 用于通过所述 P-CSCF与移动性管理实体 MME之间的 第二类型的第一信令消息, 接收终端设备发送给应用服务器的上行数据; 所 述第二类型的第一信令消息是所述 MME接收到基站发送的第一类型的第一 信令消息后, 根据所述第一类型的第一信令消息中的所述上行数据生成的, 所述第二类型的第一信令消息包括所述上行数据, 所述上行数据的数据量小 于预设数据量门限;
第四发送模块, 用于将所述上行数据发送给 S-CSCF, 以使所述 S-CSCF 将所述上行数据发送给所述应用服务器。
在第十一方面的第一种可能的实现方式中, 所述第四接收模块还用于在 接收所述上行数据之前, 通过所述 P-CSCF与所述 MME之间的第二类型的 第二信令消息, 接收所述 MME发送的第一 SIP注册请求消息, 并在所述第 四发送模块将所述第一 SIP注册请求消息发送给所述应用服务器后, 接收所 述 S-CSCF发送的所述应用服务器在接收到所述终端设备对应的 SIP标识返 回的第一 SIP注册完成消息, 所述第一 SIP注册请求消息包括所述终端设备 的标识和所述终端设备对应的 SIP标识;
所述第四发送模块还用于在所述第四接收模块接收到所述第一 SIP注册 请求消息后, 将所述第一 SIP 注册请求消息发送给所述 S-CSCF, 以使所述 S-CSCF将所述第一 SIP注册请求消息发送给所述应用服务器,以及在所述第 四接收模块接收到所述第一 SIP注册完成消息后, 通过所述 P-CSCF与所述 MME之间的第二类型的第三信令消息,向所述 MME发送所述第一 SIP注册 完成消息。
在第十一方面的第二种可能的实现方式中, 所述第四接收模块还用于在 接收所述上行数据之前, 通过所述 P-CSCF与所述 MME之间的第二类型的 第二信令消息, 接收所述 MME发送的第二 SIP注册请求消息, 以及在所述 第四发送模块将所述第二 SIP注册请求消息发送给所述 S-CSCF后, 接收所 述 S-CSCF发送的所述应用服务器在接收到所述 MME对应的 SIP标识后返回 的第二 SIP注册完成消息, 所述第二 SIP注册请求消息包括所述 MME的标 识和所述 MME对应的 SIP标识;
所述第四发送模块还用于在所述第四接收模块接收到所述第二 SIP注册 请求消息后, 将所述第二 SIP 注册请求消息发送给所述 S-CSCF, 以使所述 S-CSCF将所述第二 SIP注册请求消息发送给所述应用服务器,以及在所述第 四接收模块接收到所述第二 SIP注册完成消息后, 通过所述 P-CSCF与所述 MME之间的第二类型的第三信令消息,向所述 MME发送所述第二 SIP注册 完成消息。
结合第十一方面的第二种可能的实现方式, 在第十一方面的第三种可能 的实现方式中, 所述第四接收模块还用于接收所述 S-CSCF发送的所述应用 服务器发送给终端设备的下行数据和所述 MME的地址信息, 所述 MME的 地址信息是所述 S-CSCF根据所述终端设备对应的 SIP标识查询归属存储服 务器 HSS获取的,所述 HSS存储有所述终端设备的标识与所述终端设备对应 的 SIP标识之间的映射关系, 以及所述终端设备的标识与所述 MME的地址 信息之间的映射关系;
所述第四发送模块还用于在所述第四接收模块接收到所述下行数据和所 述 MME的地址信息后,根据所述 MME的地址信息,通过所述 P-CSCF与所 述 MME之间的第二类型的第四信令消息 , 向所述 MME发送所述下行数据。 结合第十一方面或第十一方面的第一种可能的实现方式或第十一方面的 第二种可能的实现方式或第十一方面的第三种可能的实现方式, 在第十一方 面的第四种可能的实现方式中, 所述第四接收模块用于通过所述 P-CSCF与 移动性管理实体 MME之间的第二类型的第一信令消息, 接收终端设备发送 给应用服务器的上行数据包括:
所述第四接收模块具体用于接收 MSC服务器发送的所述第二类型的第 一信令消息, 所述第二类型的第一信令消息是所述 MSC 服务器根据所述 MME发送的第三类型的第一信令消息生成的,所述第三类型的第一信令消息 包括所述上行数据。
结合第十一方面的第三种可能的实现方式, 在第十一方面的第五种可能 的实现方式中, 所述第四发送模块用于根据所述 MME的地址信息, 通过所 述 P-CSCF与所述 MME之间的第二类型的第四信令消息,向所述 MME发送 所述下行数据包括:
所述第四发送模块具体用于向 MSC 服务器发送的所述第二类型的第四 信令消息,以使所述 MSC服务器将所述第二类型的第四信令消息中的所述下 行数据封装在第三类型的第二信令消息中发送给所述 MME。
本发明实施例第十二方面提供一种代理呼叫会话控制功能, 包括: 接收器, 用于通过所述 P-CSCF与移动性管理实体 MME之间的第二类 型的第一信令消息, 接收终端设备发送给应用服务器的上行数据; 所述第二 类型的第一信令消息是所述 MME接收到基站发送的第一类型的第一信令消 息后, 根据所述第一类型的第一信令消息中的所述上行数据生成的, 所述第 二类型的第一信令消息包括所述上行数据, 所述上行数据的数据量小于预设 数据量门限;
发送器, 用于将所述上行数据发送给 S-CSCF, 以使所述 S-CSCF将所述 上行数据发送给所述应用服务器。
本发明实施例第十三方面提供一种数据传输系统, 包括: 本发明实施例 第五方面提供的任一终端设备、 本发明实施例第七方面提供的任一基站、 本 发明实施例第九方面提供的任一移动性管理实体 MME和本发明实施例第十 一方面提供的任一代理呼叫会话控制功能 P-CSCF;所述 P-CSCF与所述 MME 连接。
本发明实施例提供的数据传输方法、 设备及系统, 基于 MME与终端设 备之间的第一类型的信令消息和 MME与 P-CSCF之间的第二类型的信令消 息进行小数据的传输, 无需专门建立或恢复终端设备与网络空口侧的用户面 RAB, 节约了网络资源。 附图说明 为了更清楚地说明本发明实施例或现有技术中的技术方案, 下面将对实 施例或现有技术描述中所需要使用的附图作一简单地介绍, 显而易见地, 下 面描述中的附图是本发明的一些实施例, 对于本领域普通技术人员来讲, 在 不付出创造性劳动性的前提下, 还可以根据这些附图获得其他的附图。
图 1 为本发明以下各实施例所基于的实现小数据传输的一种系统架构 图;
图 2为本发明一实施例提供的数据传输方法的流程图;
图 3为本发明另一实施例提供的数据传输方法的流程图;
图 4为本发明又一实施例提供的数据传输方法的流程图;
图 5为本发明各实施例所基于的实现小数据传输的另一种系统架构图; 图 6为本发明又一实施例提供的数据传输方法的流程图;
图 7为本发明各实施例所基于的实现小数据传输的又一种系统架构图; 图 8为本发明一实施例提供的小数据传输方法的流程图;
图 9A为本发明一实施例提供的注册方法的流程图;
图 9B为本发明另一实施例提供的注册方法的流程图;
图 9C为本发明又一实施例提供的注册方法的流程图;
图 9D为本发明另一实施例提供的小数据传输方法的流程图;
图 10为本发明又一实施例提供的小数据传输方法的流程图;
图 11为本发明一实施例提供的终端设备的结构示意图;
图 12为本发明另一实施例提供的终端设备的结构示意图;
图 13为本发明一实施例提供的基站的结构示意图;
图 14为本发明另一实施例提供的基站的结构示意图;
图 15为本发明一实施例提供的 MME的结构示意图; 图 16为本发明另一实施例提供的 MME的结构示意图;
图 17为本发明一实施例提供的 P-CSCF的结构示意图;
图 18为本发明另一实施例提供的 P-CSCF的结构示意图。 具体实施方式 为使本发明实施例的目的、 技术方案和优点更加清楚, 下面将结合本发 明实施例中的附图, 对本发明实施例中的技术方案进行清楚、 完整地描述, 显然, 所描述的实施例是本发明一部分实施例, 而不是全部的实施例。 基于 本发明中的实施例, 本领域普通技术人员在没有作出创造性劳动前提下所获 得的所有其他实施例, 都属于本发明保护的范围。
为解决现有技术中需要为各种小数据传输创建 RAB 并预留进行数据传 输所需的资源造成网络资源浪费的问题, 本发明以下实施例提供了新的数据 传输方法, 该方法使用信令消息传输小数据, 不需要再为小数据的传输创建 用户面 RAB, 也不需要为传输小数据预留相应的资源, 既解决了小数据的传 输, 又解决了现有技术中传输小数据造成资源浪费的问题。
在此说明,本发明各实施例中的小数据可以是 MTC中下的小数据,也可 以是其他通信系统中的小数据。 所谓小数据是指数据量小于预设数据量门限 的数据。 其中, 预设数据量门限可以根据不同通信系统或需求而自行设置, 本实施例对其具体数值不做限定。
图 1 为本发明以下各实施例所基于的实现小数据传输的一种系统架构 图。 如图 1 所示, 本实施例的系统包括: 基站、 移动性管理实体(Mobility Management Entity, 简称为 MME ) 、 月良务网关(Serving Gateway, 简称为 SGW ) 、 PGW、 归属用户服务器( Home Subscriber Server, 简称为 HSS ) 、 代理呼叫会话控制功能 ( Proxy-Call Session Control Function , 简称为 P-CSCF ) 、 服务呼叫会话控制功能( Serving - Call Session Control Function, 简称为 S-CSCF )和 AS, 其中, MME、 PGW、 SGW是无线演进网络的核心 网中的三个功能实体, P-CSCF 和 S-CSCF是 IMS网络的核心处理部件, 用 来控制用户注册、 会话控制等功能。 S-CSCF在整个 IMS核心网的会话控制 过程中处于核心控制地位, 接受来自拜访网络的 IMS终端经过 P-CSCF转发 的注册请求, 与 HSS配合对 IMS终端用户进行鉴权, 并从 HSS中下载 IMS 基本签约数据,执行针对主叫端及被叫端 IMS终端用户的基本会话路由功能。 可选的, 如图 1所示, 该架构还包括: 用户设备(User Equipment, 简称 为 UE )和共用数据网 (Public Data Network, 简称为 PDN ) 。 本发明各实施 例中的 UE可以是各种小数据传输终端或低数据流量终端, 例如可以是 MTC 终端, 但不限于此。 另外, 本发明各实施例的 UE除了可以传输小数据之夕卜, 也可以有大数据传输。 所谓大数据是相对 d、数据来说的。
如图 1所示, UE与基站相连, 两者之间的接口为 Uu接口;基站与 MME 相连, 两者之间的接口为 S1-MME接口; 基站与 SGW相连, 两者之间的接 口为 S1-U接口; SGW与 PGW相连, 两者之间的接口为 S5/S8接口; PGW 与 PDN相连, 两者之间的接口为 SGi接口; SGW与 MME相连, 两者之间 的接口为 SI 1接口; MME与 HSS相连,两者之间的接口为 S6a接口; P-CSCF 与 MME相连; P-CSCF与 S-CSCF相连; S-CSCF与 HSS相连, 两者之间的 接口为 Cx接口; AS与 S-CSCF相连。 AS作为小数据传输系统中的应用服务 器, 其与 S-CSCF之间的连接关系, 视小数据传输系统的结构而定。 例如, 假设小数据传输系统为 MTC系统, 则 AS可以直接与 S-CSCF连接, 也可以 通过 MTC系统中的 SCS与 S-CSCF连接, 还可以通过 SCS和 MTC-IWF与 S-CSCF连接。 其中, 可将 AS与 S-CSCF之间的接口或者 SCS与 S-CSCF之 间的接口称为 ISC接口, 将 SCS 和 MTC-IWF之间接口称为 Tsp接口。
上面提到的各接口的名称并不限于此, 本实施例仅以此为例进行说明。 其中, 上述 Cx接口可以釆用 Diameter协议实现, Diameter协议是远端鉴权 拨入用户服务( Remote Authentication Dial In User Service , 简称为 RADIUS ) 协议的升级版本, 该 Cx接口主要功能包括 S-CSCF与 HSS之间鉴权信息和 签约信息的交互, 以及查询用户指派的 S-CSCF信息等; Tsp接口主要用以传 输设备触发等相关的控制面信令; ISC接口可以釆用会话初始协议(Session Initiation Protocol, 简称为 SIP ) 实现, S-CSCF通过该接口与 AS进行通信, 以实现对小数据业务的支持。
在此说明, 本发明各实施例中提及的 "相连或连接" 包括直接相连或连 接, 也包括经过其他设备或网元实现的间接相连或连接。
如图 1所示,该架构实现了小数据传输系统和 IMS网络的接口,通过 IMS 网元来支持小数据传输系统中小量数据的传输。 另外, 在图 1 中, MME和 P-CSCF相连接, 而不是由 PGW连接至 P-CSCF, 这为小数据在 UE和 MME 之间通过信令消息进行传输提供了条件, 使得小数据传输可以不用建立默认 用户面 RAB。 下面将以图 1所示系统架构为例, 说明本发明实施例提供的数 据传输方法的流程。
图 2为本发明一实施例提供的数据传输方法的流程图。 本实施例是从终 端设备的角度进行说明的。 如图 1所示, 本实施例的方法包括:
步骤 101、 终端设备判断待发送上行数据的数据量是否小于预设数据量 门限, 如果判断结果为是, 即上行数据的数据量小于预设数据量门限, 则执 行步骤 102; 如果判断结果为否, 可选的, 终端设备可以按照现有技术中的 发送流程发送上行数据。
在本发明各实施例中, 将由终端设备发往应用服务器的数据称为上行数 据, 相应地, 将由应用服务器发送终端设备的数据称为下行数据。
具体的, 当终端设备需要向应用服务器发送上行数据时, 判断待发送的 上行数据的数据量是否为小数据, 该判断过程具体为判断待发送上行数据的 数据量是否小于预设数据量门限, 如果判断结果为是, 说明待发送的上行数 据为小数据, 如果判断结果为否, 说明待发送的上行数据不是小数据(即是 大数据) 。 当判断出待发送的上行数据为小数据时, 终端设备继续执行后续 步骤以釆用信令的方式进行传输; 当判断出待发送的上行数据不是小数据时, 终端设备釆用数据的方式进行传输。 若釆用数据的方式进行传输属于现有常 规流程, 即需要建立用户面 RAB, 该过程可参见现有流程, 在本实施例不再 细述。
步骤 102、 终端设备向基站发送 RRC连接请求消息, 该 RRC连接请求 消息包括指示基站仅为终端设备建立信令连接的指示信息。
可选的, 上述指示信息可以用 RRC连接请求消息中的 "建立原因值" 这 一信元来携带, 但不限于此。 例如, 终端设备也可以在 RRC连接请求消息中 扩展新的字段, 或者在现有字段中增加新的信元单元( Information Element, 简称为 IE )来携带上述指示信息。
步骤 103、 终端设备接收基站发送的 RRC连接建立消息。
步骤 104、终端设备将上行数据携带在 RRC连接完成消息中发送给基站, 以使基站根据上述指示信息, 将上行数据通过基站与 MME之间的第一类型 的第一信令消息发送给 MME , 以使 MME通过 MME与 P-CSCF之间的第二 类型的第一信令消息将上行数据发送给上行数据对应的应用服务器。
上述步骤 102-步骤 104描述了终端设备与基站建立 RRC连接,并通过与 基站之间的信令消息将上行数据发送给基站的过程, 同时, 终端设备在与基 站建立 RRC连接的过程中, 指示基站仅为终端设备建立信令连接, 使得基站 以及核心网中的网元(这里主要是指 MME )仅为终端设备建立信令连接, 为 终端设备通过信令向应用服务器发送上行数据打下了基础。
对基站来说, 接收到终端设备发送的上行数据之后, 将上行数据携带在 其与 MME之间的信令消息中发送给 MME。 如图 1所示 , 本实施例的 MME 与 P-CSCF连接, 故 MME在接收到基站通过信令消息发送过来的上行数据 后, 将该上行数据携带在其与 P-CSCF之间的信令消息中发送给 P-CSCF, 使 得 P-CSCF经 S-CSCF最终将上行数据发送给应用服务器。
在上述过程中, 将基站与 MME之间使用的信令协议称为第一类型的信 令协议, 第一类型的信令协议下的信令消息称为第一类型的信令消息; 将 MME与 P-CSCF之间使用的信令协议称之为第二类型的信令协议,第二类型 的信令协议下的信令消息称为第二类型的信令消息。 为了区分第一类型的各 信令消息, 在第一类型的信令消息前面分别冠以第一、 第二、 第三、 第四、 第五等数字, 同理, 为了区分第二类型的各信令消息, 也在第二类型的信令 消息前面分别冠以第一、 第二、 第三、 第四、 第五等数字。 但是这里的 "第 一、 第二、 第三、 第四、 第五" 等数字并没有个数的含义, 也不表示先后顺 序, 仅是为了便于区分。
上述第一类型的信令协议和第二类型的信令协议可以是同一信令协议, 也可以是不同的信令协议。 较为优选的, 第一类型的信令协议为非接入层信 令( Non Access Stratum, 简称为 NAS )协议, 第二类型的信令协议为 SIP。
在上述数据发送过程中, MME与 UE之间仅存在信令连接, 而不存在用 户面 RAB。
在本实施例中, 终端设备在判断出待发送的上行数据为小数据时, 决定 选择信令的方式进行传输, 于是在与基站建立 RRC连接的过程中, 指示基站 仅为终端设备建立信令连接, 进而通过基站与 MME之间的第一类型的第一 信令消息以及 MME与 P-CSCF之间的第二类型的第一信令消息将上行数据 发送给应用服务器, MME与终端设备之间不需要建立用户面 RAB, 也不需 要为终端设备预留传输小数据所需的其他资源, 解决了网络资源, 有利于将 网络资源充分用于大数据的传输。
进一步, 现有技术中为了节约无线资源和减少终端设备的耗电, 如果终 端设备在一段时间内未与网络侧进行业务交互, 即没有进行信令交互和用户 面 RAB交互,则网络侧会释放在空口一侧与终端设备之间的信令连接和用户 面 RAB, 此时终端设备会处于空闲状态(英文为 Idle State ) , 当终端设备需 要发送或者接收用户面数据时,终端设备需要首先恢复与网络侧的信令连接, 然后通过信令连接恢复与网络侧的用户面 RAB, 此时终端设备会处于连接状 态 (英文为 Connected State ) 。 上述过程对于一些小数据量业务而言, 每次 业务只需要传输很少量的用户面数据, 处于空闲状态的终端设备每次都需要 执行恢复信令连接, 进而通过信令连接恢复空口侧用户面 RAB, 导致增加了 信令开销, 加重了网络负荷, 增加了运营商的运营成本。 本实施例的方法通 过信令进行小数据传输, 不需要建立用户面 RAB, 也就不需要恢复用户面 RAB, 可以解决上述问题, 有利于减轻网络负担, 降低运营商的运营成本, 还有利于提高小数据的传输速率。
在进行小数据传输之前, 终端设备或由 MME代替终端设备需要向应用 服务器进行注册。 基于此, 在一可选实施方式中, 终端设备判断待发送上行 数据的数据量是否小于预设数据量门限之前可以包括:
终端设备向 MME发送附着请求消息 , 以使 MME通过 MME与 P-CSCF 之间的第二类型的第二信令消息向应用服务器发送第一 SIP注册请求消息。 其中, 附着请求消息包括终端设备的标识, 例如终端设备的标识可以是终端 设备的国际移动用户识另1 J码 ( International Mobile Subscriberldentification Number, 简称为 IMSI )。 第一 SIP注册请求消息包括上述终端设备的标识和 终端设备对应的 SIP标识。
终端设备接收 MME发送的附着接受消息, 该附着接受消息是 MME通 过 MME与 P-CSCF之间的第二类型的第三信令消息接收应用服务器返回的 第一 SIP注册完成消息后生成的, 第一 SIP注册完成消息是应用服务器在接 收到终端设备对应的 SIP标识后返回的。
上述过程为终端设备执行 EPS附着流程的过程, 在该实施方式中, 所述 附着流程包括鉴权和位置更新操作等, 但不创建默认承载, 即终端设备与
MME之间仅存在信令连接。 在该附着流程中, MME作为用户代理(英文为 user agent ) 与 IMS系统及 AS交互,代替终端设备完成向应用服务器的注册 流程, MME代替终端设备向应用服务器进行注册的过程对终端设备与 MME 之间的第一类型的信令交互不受影响。 在该实施方式中, 终端设备无需 IP地 址, 且终端设备上也不需要存储自身对应的 SIP标识。 第一 SIP注册请求消 息中的终端设备对应的 SIP标识可以是 HSS在附着流程中返回给 MME的 , HSS上存储有终端设备的标识与终端设备对应的 SIP标识之间的映射关系。 另外, 第一 SIP注册请求消息中的终端设备对应的 SIP标识也可以是 MME 根据终端设备的标识为终端设备分配的。
在进行小数据传输之前, 终端设备或由 MME代替终端设备需要向应用 服务器进行注册。 基于此, 在另一可选实施方式中, 终端设备判断待发送上 行数据的数据量是否小于预设数据量门限之前可以包括:
终端设备向 MME发送附着请求消息, 该附着请求消息包括终端设备的 标识。
终端设备接收 MME发送的附着接受消息, 该附着接受消息包括 MME 为终端设备分配的 IP地址。
终端设备根据 MME为其分配的 IP地址, 通过终端设备与 MME之间的 第一类型的第二信令消息向 MME发送第一 SIP注册请求消息, 以使 MME 通过 MME与 P-CSCF之间的第二类型的第二信令消息,将第 ― SIP注册请求 消息发送给应用服务器。 其中, 第一 SIP注册请求消息包括终端设备的标识 和终端设备对应的 SIP标识。
终端设备通过终端设备与 MME之间的第一类型的第三信令消息, 接收 MME返回的第一 SIP注册完成消息,第一 SIP注册完成消息是应用服务器在 接收到终端设备对应的 SIP 标识后返回的。 其中, MME 是通过 MME 与 P-CSCF之间的第二类型的第三信令消息接收到第一 SIP注册完成消息的。
上述过程为终端设备执行 EPS附着流程的过程, 在该实施方式中, 所述 附着流程包括鉴权和位置更新操作等, 但不创建默认承载, 即终端设备与 MME之间仅存在信令连接。 在该附着流程中, 由 MME给终端设备分配 IP 地址, 终端设备上预先存储有终端设备对应的 SIP标识, 终端设备自身作为 用户代理(user agent ) 向应用服务器发起 SIP注册流程, 通过将第一 SIP注 册请求消息封装在第一类型的信令消息中发送给 MME, 然后通过 MME 与 P-CSCF之间的第二类型的信令消息传输给应用服务器,从而实现 SIP注册流 程, 为后续终端设备与应用服务器进行数据传输打下基础。
上述终端设备预先存储对应的 SIP标识的方式包括但不限于: 终端设备 在出厂时预置对应的 SIP标识, 或者, 由网络侧 (主要是指 P-CSCF )预先向 终端设备发送信令消息, 为其配置对应的 SIP标识。
在进行小数据传输之前, 终端设备或由 MME代替终端设备向应用服务 器进行注册。 基于此, 在又一可选试试方式中, 终端设备判断待发送上行数 据的数据量是否小于预设数据量门限之前可以包括:
终端设备向 MME发送附着请求消息, 该附着请求消息包括终端设备的 标识。
终端设备接收 MME发送的附着接受消息。
上述过程为终端设备执行 EPS附着流程的过程, 在该实施方式中, 所述 附着流程包括鉴权和位置更新操作等, 但不创建默认承载, 即终端设备与 MME之间仅存在信令连接。 在该附着流程之前, MME预先向应用服务器进 行注册, 不再需要该 MME下每个终端设备向应用服务器注册, 可以减少向 应用服务器的注册次数, 节约资源。
在本实施例的一可选实施方式中, 终端设备除了向应用服务器发送上行 数据之外, 终端设备也可以接受应用服务器发送的下行数据。 终端设备接收 应用服务器发送的下行数据的过程可以包括:
终端设备接收 MME发送的寻呼消息, 该寻呼消息是 MME通过 MME 与 P-CSCF之间的第二类型的第四信令消息在接收到应用服务器发送给终端 设备的下行数据后生成的。
终端设备根据上述寻呼消息, 向 MME发送服务请求消息, 该服务请求 消息用于指示 MME仅为终端设备建立信令连接。
终端设备接收 MME根据服务请求消息发送的第一类型的第四信令消息, 该第一类型的第四信令消息包括上述下行数据。
在该实施方式中, 应用服务器发送给终端设备的下行数据也通过 MME 通过与 P-CSCF之间的第二类型的信令消息以及 MME与终端设备之间的第 一类型的信令消息完成, 同样可以使 MME与终端设备之间仅存在信令连接, 不需要为终端设备建立用户面 RAB, 同样有利于节约网络资源。
在此说明, 在上述各实施方式中, 终端设备与 MME之间的交互需要通 过基站进行, 由于基站在上述各过程中仅起到中转作用, 为简化描述将其省 略。
图 3为本发明另一实施例提供的数据传输方法的流程图。 本实施例从基 站的角度进行描述。 如图 3所示, 本实施例的方法包括:
步骤 301、 基站接收终端设备发送的 RRC连接请求消息, 该 RRC连接 请求消息是终端设备判断出待发送上行数据的数据量小于预设数据量门限时 生成的,该 RRC连接请求消息包括指示基站仅为终端设备建立信令连接的指 示信息。
步骤 302、 基站向终端设备发送 RRC连接建立消息。
步骤 303、 基站接收终端设备发送的 RRC连接完成消息, 该 RRC连接 完成消息包括上述上行数据。
步骤 304、基站根据上述指示信息,通过基站与 MME之间的第一类型的 第一信令消息将上行数据发送给 MME,以使 MME通过所述 MME与 P-CSCF 之间的第二类型的第一信令消息将上行数据发送给上行数据对应的应用服务 器。
具体的, 当终端设备需要向应用服务器发送上行数据时, 判断待发送的 上行数据的数据量是否为小数据, 该判断过程具体为判断待发送上行数据的 数据量是否小于预设数据量门限, 如果判断结果为是, 说明待发送的上行数 据为小数据, 如果判断结果为否, 说明待发送的上行数据不是小数据(即是 大数据) 。 当判断出待发送的上行数据为小数据时, 终端设备选择釆用信令 的方式进行传输。 因此, 终端设备向基站发送 RRC连接请求消息, 以请求与 基站建立 RRC连接, 同时通过携带指示信息指示基站仅为终端设备建立信令 连接。 相应地, 基站接收终端设备发送的 RRC连接请求消息, 并向终端设备 发送 RRC连接建立消息, 以与终端设备建立 RRC。 相应地, 终端设备接收 到 RRC连接建立消息后, 通过 RRC连接完成消息将上行数据发送给基站。 基站基于上述指示信息, 将上行数据通过与 MME之间的第一类型的第一信 令消息发送给 MME, 而 MME通过其与 P-CSCF之间的第二类型的第一信令 消息发送给 P-CSCF, 进而使 P-CSCF经过 S-CSCF将上行数据发送给应用服 务器, 完成上行数据的传输。
由上述可见, 在本实施例中, 终端设备发送给应用服务器的上行数据, 是通过终端设备与基站之间的信令消息 (即 RRC 连接完成消息) 、 基站与 MME之间的信令消息以及 MME与 P-CSCF之间的信令消息完成传输的 , 使 得 MME 与终端设备之间仅需存在信令连接, 无需为终端设备建立用户面 RAB, 也无需为终端设备预留传输小数据所需的其他资源, 节约了网络资源, 同时有利于提高小数据的传输速率。
图 4为本发明又一实施例提供的数据传输方法的流程图。 本实施例是从 MME的角度进行的描述。 如图 4所示, 本实施例的方法包括:
步骤 401、 MME接收基站发送的第一类型的第一信令消息, 该第一类型 的第一信令消息是基站在接收到终端设备发送的 RRC连接完成消息后,根据 终端设备发送的 RRC连接请求消息中的指示信息生成的, 该 RRC连接完成 消息包括终端设备发送给应用服务器的上行数据, 该第一类型的第一信令消 息包括所述上行数据, 上述指示信息用于指示基站仅为终端设备建立信令连 接。
步骤 402、 MME通过 MME与 P-CSCF之间的第二类型的第一信令消息, 将上行数据发送给应用服务器。
具体的, 当终端设备需要向应用服务器发送上行数据时, 判断待发送的 上行数据的数据量是否为小数据, 该判断过程具体为判断待发送上行数据的 数据量是否小于预设数据量门限, 如果判断结果为是, 说明待发送的上行数 据为小数据, 如果判断结果为否, 说明待发送的上行数据不是小数据(即是 大数据) 。 当判断出待发送的上行数据为小数据时, 终端设备选择釆用信令 的方式进行传输。 因此, 终端设备向基站发送 RRC连接请求消息, 以请求与 基站建立 RRC连接, 同时通过携带指示信息指示基站仅为终端设备建立信令 连接。 相应地, 基站接收终端设备发送的 RRC连接请求消息, 并向终端设备 发送 RRC连接建立消息, 以与终端设备建立 RRC。 相应地, 终端设备接收 到 RRC连接建立消息后, 通过 RRC连接完成消息将上行数据发送给基站。 基站在接收到 RRC连接完成消息后从中获取上行数据,将上行数据封装在其 与 MME之间的第一类型的第一信令消息中发送给 MME。 相应地, MME接 收第一类型的第一信令消息, 从中获取上行数据, 然后将上行数据封装在其 与 P-CSCF之间的第二类型的第一信令消息中发送给 P-CSCF ,进而使 P-CSCF 经过 S-CSCF将上行数据发送给应用服务器, 完成上行数据的传输。
由上述可见, 在本实施例中, 终端设备发送给应用服务器的上行数据, 是通过终端设备与基站之间的信令消息 (即 RRC 连接完成消息) 、 基站与 MME之间的信令消息以及 MME与 P-CSCF之间的信令消息完成传输的 , 使 得 MME 与终端设备之间仅需存在信令连接, 无需为终端设备建立用户面 RAB, 也无需为终端设备预留传输小数据所需的其他资源, 节约了网络资源, 同时有利于提高小数据的传输速率。
在进行小数据传输之前, 终端设备或由 MME代替终端设备需要向应用 服务器进行注册。基于此, 在另一可选试试方式中, MME接收基站发送的第 一类型的第一信令消息之前可以包括:
首先, MME接收终端设备发送的附着请求消息,该附着请求消息包括终 端设备的标识。 终端设备的标识可以是终端设备的 IMSI, 但不限于此。
接着, MME根据终端设备的标识, 获取终端设备对应的 SIP标识, 并生 成第一 SIP注册请求消息, 该第一 SIP注册请求消息包括终端设备的标识和 终端设备对应的 SIP标识。
可选的, MME根据终端设备的标识, 获取终端设备对应的 SIP标识包括 但不限于以下方式:
MME向 HSS发送位置更新请求消息, 位置更新请求消息包括终端设备 的标识。
MME接收 HSS根据终端设备的标识返回的终端设备的标识和终端设备 对应的 SIP标识之间的映射关系。基于此, MME从终端设备的标识和终端设 备对应的 SIP标识之间的映射关系中, 获取终端设备对应的 SIP标识。 或者, MME根据终端设备的标识, 生成终端设备对应的 SIP标识。
然后 , MME通过 MME与 P-CSCF之间的第二类型的第二信令消息向应 用服务器发送第一 SIP注册请求消息。
然后 , MME通过 MME与 P-CSCF之间的第二类型的第三信令消息 , 接 收应用服务器在接收到终端设备对应的 SIP标识后返回的第一 SIP注册完成 消息。 然后, MME向终端设备发送附着接受消息, 附着接受消息包括第一 SIP 注册完成消息。
上述过程为终端设备执行 EPS附着流程的过程, 在该实施方式中, 所述 附着流程包括鉴权和位置更新操作等, 但不创建默认承载, 即终端设备与 MME之间仅存在信令连接。 在该附着流程中, MME作为用户代理(英文为 user agent ) 与 IMS系统及 AS交互,代替终端设备完成向应用服务器的注册 流程, MME代替终端设备向应用服务器进行注册的过程对终端设备与 MME 之间的第一类型的信令交互不受影响。 在该实施方式中, 终端设备无需 IP地 址, 且终端设备上也不需要存储自身对应的 SIP标识。
在进行小数据传输之前, 终端设备或由 MME代替终端设备需要向应用 服务器进行注册。基于此, 在另一可选试试方式中, MME接收基站发送的第 一类型的第一信令消息之前可以包括:
MME接收终端设备发送的附着请求消息,该附着请求消息包括终端设备 的标识。
MME为终端设备分配 IP地址。
MME向终端设备发送附着接受消息, 该附着接受消息包括 IP地址。 MME接收终端设备根据 IP地址发送的第一类型的第二信令消息, 该第 一类型的第二信令消息包括第一 SIP注册请求消息, 该第一 SIP注册请求消 息包括终端设备的标识和终端设备对应的 SIP标识。
在该过程中, 终端设备将终端设备的标识和终端设备上预先存储 SIP标 识封装在第一 SIP注册请求消息中。 终端设备上预先存储 SIP标识的方式包 括但不限于: 终端设备在出厂时预置对应的 SIP标识, 或者, 由网络侧 (主 要是指 P-CSCF )预先向终端设备发送信令消息, 为其配置对应的 SIP标识。
MME通过 MME与 P-CSCF之间的第二类型的第二信令消息 ,将第 ― SIP 注册请求消息发送给应用服务器。
MME通过 MME与 P-CSCF之间的第二类型的第三信令消息 ,接收应用 服务器在接收到终端设备对应的 SIP标识返回的第一 SIP注册完成消息。
MME向终端设备发送第一类型的第三信令消息,第一类型的第三信令消 息包括第一 SIP注册完成消息。
上述过程为终端设备执行 EPS附着流程的过程, 在该实施方式中, 所述 附着流程包括鉴权和位置更新操作等, 但不创建默认承载, 即终端设备与
MME之间仅存在信令连接。 在该附着流程中, 由 MME给终端设备分配 IP 地址, 终端设备上预先存储有终端设备对应的 SIP标识, 终端设备自身作为 用户代理(user agent ) 向应用服务器发起 SIP注册流程, 终端设备生成第一 SIP 注册请求消息, 然后将其封装在第一类型的信令消息中发送给 MME, MME接收封装有第一 SIP注册请求消息的第一类型的信令消息,然后通过其 与 P-CSCF之间的第二类型的信令消息传输给应用服务器, 从而实现 SIP注 册流程, 为后续终端设备与应用服务器进行数据传输打下基础。
在进行小数据传输之前, 终端设备或 MME代替终端设备向应用服务器 进行注册。基于此, 在一可选试试方式中, MME接收基站发送的第一类型的 第一信令消息之前可以包括:
MME通过 MME与 P-CSCF之间的第二类型的第二信令消息 ,向 P-CSCF 发送第二 SIP注册请求消息, 以使 P-CSCF将第二 SIP注册请求消息发送给 应用服务器, 该第二类型的第二信令消息包括第二 SIP注册请求消息, 该第 二 SIP注册请求消息包括 MME的标识和 MME对应的 SIP标识。
MME通过 MME与 P-CSCF之间的第二类型的第三信令消息 ,接收应用 服务器在接收到 MME对应的 SIP标识后返回的第二 SIP注册完成消息。
上述过程为 MME向应用服务器进行注册的过程, 在该过程中 MME将 自己的标识和对应的 SIP标识注册给应用服务器。
基于上述, MME通过 MME与 P-CSCF之间的第二类型的第三信令消息, 接收应用服务器在接收到 MME对应的 SIP标识后返回的第二 SIP注册完成 消息之后包括:
MME接收终端设备发送的附着请求消息,该附着请求消息包括终端设备 的标识;
MME向终端设备发送附着接受消息。
上述过程为终端设备在 MME向应用服务器完成 SIP注册流程之后, 执 行 EPS附着流程的过程, 在该实施方式中, 所述附着流程包括鉴权和位置更 新操作等, 但不创建默认承载, 即终端设备与 MME之间仅存在信令连接。 由于 MME预先向应用服务器进行了注册, 所以该 MME下的终端设备不需 要再向应用服务器进行注册, 可以减少向应用服务器的注册次数, 有利于节 约资源。
在本实施例的一可选实施方式中, 终端设备除了向应用服务器发送上行 数据之外, 终端设备也可以接受应用服务器发送的下行数据。 应用服务器发 送给终端设备的下行数据也通过 MME与 P-CSCF之间的信令消息进行传输, 无需为终端设备建立用户面 RAB, 同样有利于节约网络资源。 下行数据的传 输过程包括:
MME通过 MME与 P-CSCF之间的第二类型的第四信令消息 ,接收应用 服务器发送给终端设备的下行数据。
MME向终端设备发送寻呼消息。
MME接收终端设备发送的服务请求消息。
MME向终端设备发送第一类型的第四信令消息,第一类型的第四信令消 息包括下行数据。
具体的,应用服务器有下行数据需要发送时,将下行数据发送给 S-CSCF, 由 S-CSCF将下行数据发送给 P-CSCF, P-CSCF接收到下行数据之后, 将下 行数据封装在第二类型的第四信令消息中发送给 MME。而 MME接收第二类 型的第四信令消息, 从中解析出下行数据。 然后, MME向终端设备发送寻呼 消息, 以告知终端设备有下行数据需要向其发送。 终端设备接收到寻呼消息 后 , 向 MME发送服务请求消息 , 以请求 MME向其传输下行数据。 MME接 收到服务请求消息后, 将下行数据封装在其与终端设备之间的第一类型的第 四信令消息中发送给终端设备。 由此可见, 应用服务器发送给终端设备的下 行数据也是通过 MME与 P-CSCF之间以及 MME与终端设备之间的信令消息 完成传输的, 无需为终端设备建立用户面 RAB, 同样可以节约网络资源。
在上述各实施例中, 为了完成上行数据或下行数据的传输, 需要 MME 同时支持第一类型的信令协议和第二类型的信令协议。 如果第一类型的信令 协议和第二类型的信令协议不相同, 则需要对 MME进行改进, 使之同时支 持第一类型的信令协议和第二类型的信令协议。 为了减少对 MME的改动, 可以使用现有技术中同时支持第二类型的信令协议, 且已经实现与 MME之 间互联的网元 ,通过该网元建立起 MME和 P-CSCF之间的连接 ,减少对 MME 的改动。 以第一类型的信令协议为 NAS协议, 而第二类型的信令协议为 SIP 为例, 可以通过支持 SIP的移动交换中心 (Mobile Switching Center, 简称为 MSC )服务器将 MME与 P-CSCF连接起来。
图 5为本发明各实施例所基于的实现小数据传输的另一种系统架构图。 图 5与图 1相比, 区别在于: MME与 P-CSCF之间通过 MSC服务器连接。 MME和 MSC服务器之间的接口称为 SGs接口。 现有技术中看, MSC服务 器已经实现了与 MME的连接, 且 MSC服务器支持第二类型的信令协议, 也 已经实现了与 P-CSCF之间的互联。
基于图 5所示架构 , MME通过 MME与 P-CSCF之间的第二类型的第一 信令消息, 将上行数据发送给应用服务器包括: MME向 MSC服务器发送第 三类型的第一信令消息, 第三类型的第一信令消息包括上行数据, 以使 MSC 服务器将上行数据封装在第二类型的第一信令消息中发送给 P-CSCF,以将上 行数据发送给应用服务器。
相应地, MME通过 MME与 P-CSCF之间的第二类型的第四信令消息 , 接收应用服务器发送给终端设备的下行数据包括: MME接收 MSC服务器发 送的第三类型的第二信令消息,第三类型的第二信令消息是 MSC服务器根据 P-CSCF发送的第二类型的第四信令消息生成的,第三类型的第二信令消息包 括下行数据。
上述第三类型的信令协议可以就是第一类型的信令协议, 例如 NAS 协 议, 也可以是不同于第一类型的其他信令协议。 现有 MME 已经可以支持第 三类型的信令协议。
由上述可见, 本实施例通过重用 MME与 MSC服务器之间的连接, 通过
MSC服务器实现 MME与 P-CSCF之间的交互 , 减少了对 MME的改动。
图 6为本发明又一实施例提供的数据传输方法的流程图。 本实施例是从 P-CSCF的角度进行的描述。 如图 6所示, 本实施例的方法包括:
步骤 601、 P-CSCF通过 P-CSCF与 MME之间的第二类型的第一信令消 息, 接收终端设备发送给应用服务器的上行数据, 其中, 第二类型的第一信 令消息是 MME接收到基站发送的第一类型的第一信令消息后, 根据第一类 型的第一信令消息中的上行数据生成的, 第二类型的第一信令消息包括上行 数据, 该上行数据的数据量小于预设数据量门限。
步骤 602、 P-CSCF将上行数据发送给 S-CSCF, 以使 S-CSCF将上行数 据发送给应用服务器。 具体的, 当终端设备需要向应用服务器发送上行数据时, 判断待发送的 上行数据的数据量是否为小数据, 该判断过程具体为判断待发送上行数据的 数据量是否小于预设数据量门限, 如果判断结果为是, 说明待发送的上行数 据为小数据, 如果判断结果为否, 说明待发送的上行数据不是小数据(即是 大数据) 。 当判断出待发送的上行数据为小数据时, 终端设备选择釆用信令 的方式进行传输。 因此, 终端设备向基站发送 RRC连接请求消息, 以请求与 基站建立 RRC连接, 同时通过携带指示信息指示基站仅为终端设备建立信令 连接。 相应地, 基站接收终端设备发送的 RRC连接请求消息, 并向终端设备 发送 RRC连接建立消息, 以与终端设备建立 RRC。 相应地, 终端设备接收 到 RRC连接建立消息后, 通过 RRC连接完成消息将上行数据发送给基站。 基站在接收到 RRC连接完成消息后从中获取上行数据,将上行数据封装在其 与 MME之间的第一类型的第一信令消息中发送给 MME。 相应地, MME接 收第一类型的第一信令消息, 从中获取上行数据, 然后将上行数据封装在其 与 P-CSCF 之间的第二类型的第一信令消息中发送给 P-CSCF。 相应地, P-CSCF接收第二类型的第一信令消息,从中获取上行数据, 然后将上行数据 发送给 S-CSCF, 以使 S-CSCF将上行数据发送给应用服务器, 完成上行数据 的传输。
由上述可见, 在本实施例中, 终端设备发送给应用服务器的上行数据, 是通过终端设备与基站之间的信令消息 (即 RRC 连接完成消息) 、 基站与 MME之间的信令消息以及 MME与 P-CSCF之间的信令消息完成传输的 , 使 得 MME 与终端设备之间仅需存在信令连接, 无需为终端设备建立用户面 RAB, 也无需为终端设备预留传输小数据所需的其他资源, 节约了网络资源, 同时有利于提高小数据的传输速率。
在进行上行数据传输之前, 终端设备或由 MME代替终端设备需要预先 向应用服务器进行注册。基于此,在一可选实施方式中, P-CSCF通过 P-CSCF 与 MME之间的第二类型的第一信令消息, 接收终端设备发送给应用服务器 的上行数据之前包括:
P-CSCF通过 P-CSCF与 MME之间的第二类型的第二信令消息, 接收 MME发送的第一 SIP注册请求消息,第一 SIP注册请求消息包括终端设备的 标识和终端设备对应的 SIP标识。 P-CSCF将第一 SIP注册请求消息发送给 S-CSCF, 以使 S-CSCF将第一 SIP注册请求消息发送给应用服务器。
P-CSCF接收 S-CSCF发送的应用服务器在接收到终端设备对应的 SIP标 识返回的第一 SIP注册完成消息。
P-CSCF通过 P-CSCF与 MME之间的第二类型的第三信令消息 ,向 MME 发送第一 SIP注册完成消息。
上述过程为终端设备向应用服务器进行注册的过程。 该注册过程可以是 终端设备在执行 EPS附着流程中,由 MME作为用户代理(英文为 user agent ) 与 IMS系统及应用服务器交互,代替终端设备向应用服务器进行的注册流程。 其中, MME代替终端设备向应用服务器进行注册的过程对终端设备与 MME 之间的第一类型的信令交互不受影响。 在该实施方式中, 终端设备无需 IP地 址, 且终端设备上也不需要存储自身对应的 SIP标识。 第一 SIP注册请求消 息是由 MME生成的, 该第一 SIP注册请求消息中的终端设备对应的 SIP标 识可以是 HSS在附着流程中返回给 MME的, HSS上存储有终端设备的标识 与终端设备对应的 SIP标识之间的映射关系; 或者, 第一 SIP注册请求消息 中的终端设备对应的 SIP标识也可以是 MME根据终端设备的标识为终端设 备分配的。
另夕卜,上述注册过程也可以是终端设备在执行 EPS附着流程中,由 MME 为终端设备分配 IP地址后, 终端设备自身作为用户代理(user agent )向应用 服务器发起的 SIP注册流程。 在该实施方式中, 第一 SIP注册请求消息是终 端设备生成, 然后发送给 MME的。 第一 SIP注册请求消息中终端设备对应 的 SIP标识可以是终端设备上预先存储的。
在进行上行数据传输之前, 终端设备或由 MME代替终端设备需要预先 向应用服务器进行注册。基于此,在一可选实施方式中, P-CSCF通过 P-CSCF 与 MME之间的第二类型的第一信令消息, 接收终端设备发送给应用服务器 的上行数据之前包括:
P-CSCF通过 P-CSCF与 MME之间的第二类型的第二信令消息, 接收 MME发送的第二 SIP注册请求消息, 第二 SIP注册请求消息包括 MME的标 识和 MME对应的 SIP标识。
P-CSCF将第二 SIP注册请求消息发送给 S-CSCF, 以使 S-CSCF将第二 SIP注册请求消息发送给应用服务器。
P-CSCF接收 S-CSCF发送的应用服务器在接收到 MME对应的 SIP标识 后返回的第二 SIP注册完成消息。
P-CSCF通过 P-CSCF与 MME之间的第二类型的第三信令消息 ,向 MME 发送第二 SIP注册完成消息。
上述为 MME在终端设备执行附着流程之前, 作为用户代理向应用服务 器进行 SIP注册的过程。 在该过程中, 第二 SIP注册请求消息是 MME生成 并发送的。 在本实施方式中, MME预先向应用服务器进行注册, 不再需要该 MME 下每个终端设备向应用服务器注册, 可以减少向应用服务器的注册次 数, 节约资源。
在本实施例的一可选实施方式中, 终端设备除了向应用服务器发送上行 数据之外, 终端设备也可以接受应用服务器发送的下行数据。 应用服务器发 送的下行数据给终端设备的过程包括: P-CSCF接收 S-CSCF发送的应用服务 器发送给终端设备的下行数据和 MME的地址信息;然后, P-CSCF根据 MME 的地址信息 , 通过 P-CSCF与 MME之间的第二类型的第四信令消息向 MME 发送下行数据。
其中, MME的地址信息是 S-CSCF根据终端设备对应的 SIP标识查询 HSS获取的, HSS存储有终端设备的标识与终端设备对应的 SIP标识之间的 映射关系, 以及终端设备的标识与 MME的地址信息之间的映射关系。 具体 的, S-CSCF根据终端设备对应的 SIP标识查询 HSS ,获取与终端设备的标识, 然后根据终端设备的标识获取 MME的地址信息。
基于图 5所示系统架构, P-CSCF通过 P-CSCF与 MME之间的第二类型 的第一信令消息, 接收终端设备发送给应用服务器的上行数据包括: P-CSCF 接收 MSC服务器发送的第二信令消息, 第二信令消息是 MSC服务器根据 MME发送的第三类型的第一信令消息生成的,第三类型的第一信令消息包括 上行数据。
相应地, P-CSCF根据 MME的地址信息, 通过 P-CSCF与 MME之间的 第二类型的第四信令消息, 向 MME发送下行数据包括: P-CSCF向 MSC服 务器发送的第二类型的第四信令消息,以使 MSC服务器将第二类型的第四信 令消息中的下行数据封装在第三类型的第二信令消息中发送给 MME。 由上述可见, 应用服务器发送给终端设备的下行数据也通过 MME通过 与 P-CSCF之间的第二类型的信令消息以及 MME与终端设备之间的第一类 型的信令消息完成, 同样可以使 MME与终端设备之间仅存在信令连接, 不 需要为终端设备建立用户面 RAB, 同样有利于节约网络资源。
以小数据传输系统为 MTC系统为例,则图 1所示的实现小数据传输的系 统架构具体如图 7所示。 在图 7中, 假设移动核心网中各网元之间釆用 NAS 信令, 而 IMS系统釆用 SIP。 下面将对基于图 7所示系统架构实现的小数据 传输过程进行详细说明。
图 8为本发明一实施例提供的小数据传输方法的流程图。 该实施例以终 端设备向应用服务器发送上行数据为例。 如图 8所示, 本实施例的方法包括: 步骤 8a、 终端设备判断待发送的上行数据是否为小数据, 在判断出待发 送的上行数据为小数据时, 决定通过信令的方式进行小数据发送。
具体的, 终端设备可根据数据量大小选择釆用信令的方式或数据方式进 行发送, 如果待发送上行数据的数据量小于预设数据量门限, 则终端设备选 择釆用信令的方式; 如果待发送上行数据的数据量大于或等于预设数据量门 限, 则终端设备选择釆用数据的方式。 若釆用数据的方式则釆用常规流程, 即需要为终端设备建立用户面 RAB。
步骤 8b、终端设备向基站发送 RRC连接请求消息,请求建立 RRC连接, 该 RRC连接请求消息携带的信元 "建立原因值"指示基站仅为终端设备建立 信令连接。
步骤 8c、 基站向终端设备发送 RRC连接建立消息, 指示终端设备建立 RRC连接。
步骤 8d、 终端设备向基站发送 RRC连接完成消息, 该 RRC连接完成消 息携带 NAS协议数据单元( Protocol Data Unit, 简称为 PDU ) , 待发送上行 数据封装在 NAS PDU中。
其中, ΜΜΕ 与终端设备之间保持信令连接, 而不创建或者恢复用户面 RAB。
步骤 8e、 基站通过初始 UE消息将 NAS PDU发送给 MME。
其中, 初始 UE消息为一种 NAS信令消息, 相当于上述第一类型的第一 信令消息。 步骤 8f、 终端设备通过基站与 MME、 HSS等进行鉴权和安全流程。 该过程属于现有技术, 在此不再赘述。
步骤 8g、 MME从初始 UE消息中获取上行数据, 并将上行数据封装在 信息 (英文为 MESSAGE ) 消息中发送给 P-CSCF。
步骤 8h、 P-CSCF转发信息 (MESSAGE ) 消息到 S-CSCF。
步骤 8i、 S-CSCF基于初始过滤准则,触发向 SCS/AS的信息( MESSAGE ) 消息传输。
上述 MESSAGE消息为一种 SIP信令消息, 相当于上述第二类型的第一 信令消息。
其中, 初始过滤准则 (initial Filter Criteria, 简称为 iFC)提供业务触发能 力。 用户完成 IMS注册时, 初始过滤准则以及指定应用服务器 AS的地址已 经下载到相应的 S-CSCF中。 S-CSCF基于初始过滤准则, 触发向 SCS/AS的 信息 (MESSAGE ) 消息传输, 把该信息消息转发到指定的 AS应用服务器。
步骤 8j、 S-CSCF发送 200 OK消息给 P-CSCF。
步骤 8k、 P-CSCF转发 200 OK消息给 MME。
上述 200 OK消息为一种 SIP信令消息,相当于第二类型的第五信令消息, 用于告知 P-CSCF、 MME、 终端设备等上行数据已经成功传输到 AS。
步骤 81、 MME通过下行 NAS传输消息发送确认消息给基站。
下行 NAS传输消息属于 NAS信令消息, 相当于第一类型的第五信令消 息, 用于携带确认消息, 以告知基站和终端设备上行数据已成功传输到 AS。
步骤 8m、 基站通过下行信息传输消息传送确认消息给终端设备。
步骤 8n、 如果规定时间内没有其他数据发送, 则基站译放与终端设备之 间的 RRC连接以及与 MME之间的 S1信令连接。
在进行上述小数据传输之前, 需要先向 SCS/AS进行注册。 其中, 一种 可选的注册流程如图 9A所示, 具体包括:
步骤 9a、 终端设备向 MME发起附着请求消息, 该附着请求消息携带有 终端设备的 IMSI。
步骤 9b、 MME为终端设备执行 EPS附着流程, 该附着流程包括: 鉴权 和位置更新操作等, 但不创建默认承载 。
可选的, 在该步骤 9b中, HSS可以向 MME返回该终端设备的 IMSI和 终端设备对应的 SIP标识的映射关系。 在该实施方式中, 终端设备上不需要 存储其对应的 SIP标识,只需在签约数据中增加终端设备的 IMSI与终端设备 对应的 SIP标识之间的映射关系, 并将该映射关系存储到 HSS上即可。
可选的, MME可以根据终端设备的 IMSI, 生成该终端设备对应的 SIP 标识。
步骤 9c、 MME判断出该终端设备需进行 IMS注册, 故发起 P-CSCF发 现流程。
步骤 9d、 MME使用终端设备对应的 SIP 标识生成第一 SIP注册请求消 息, 然后封装在注册(英文为 REGISTER ) 消息中发送给上述步骤发现的 P-CSCF,即发起 SIP注册流程。第一 SIP 注册请求消息包括终端设备的 IMSI 和终端设备对应的 SIP标识。
步骤 9e、 P-CSCF根据终端设备对应的 SIP标识, 确定该终端设备来自 于拜访网络, 是要进行注册的, 故向 DNS服务器发起对终端设备的归属网络 中的 I-CSCF地址的 DNS查询,然后根据 DNS查询结果,将注册( REGISTER ) 消息发送给 I-CSCF。
其中, 终端设备对应的 SIP标识中的一部分, 用于标识该终端设备来自 哪个网络(即存储有终端设备所属网络对应的域名 ) , 而 P-CSCF上还存储 有所属的 IMS网络的域名, 故 P-CSCF根据终端设备对应的 SIP标识, 可以 确定出该终端设备是否来自于拜访网络。 所谓拜访网络是指除 P-CSCF所属 的 IMS网络之外的其他网络。
步骤 9f、 I-CSCF向 HSS发送 Cx查询。
步骤 9g、 HSS检查终端设备对应的用户的注册状态, 根据签约数据确认 该用户是否允许注册, HSS返回 Cx查询响应, 即返回 S-CSCF需要的能力, I-CSCF根据 HSS返回的结果选择一个合适的 S-CSCF。
步骤 9h、 I-CSCF发送注册(REGISTER ) 消息给上述选择的 S-CSCF。 步骤 9i、 S-CSCF接收到注册( REGISTER ) 消息之后, 通过 Cx接口向 HSS进行交互, 获取鉴权向量及用户签约信息等。
步骤 9j、 S-CSCF将注册(REGISTER )消息发送给 AS, 触发向 SCS/AS 的注册。
步骤 9k、 SCS/AS在接收到注册( REGISTER )消息后, 向 S-CSCF返回 200 ok消息, 以完成注册。
上述注册消息为一种 SIP信令消息, 相当于上述第二类型的第二信令消 息。
步骤 91、 S-CSCF向 P-CSCF返回 200 ok消息。
步骤 9m、 P-CSCF向 MME返回 200 ok消息。
上述 200 ok消息携带有第一 SIP注册完成消息, 是一种 SIP信令消息, 相当于上述第二类型的第三信令消息。
步骤 9n、 MME向终端设备发送附着接受消息, 所述附着接受消息包括 第一 SIP注册完成消息。
在该实施方式中, 所述附着流程包括鉴权和位置更新操作等, 但不创建 默认承载,即终端设备与 MME之间仅存在信令连接。在该附着流程中, MME 作为用户代理(英文为 user agent ) 与 IMS系统及 AS交互, 代替终端设备 完成向应用服务器的注册流程, MME代替终端设备向应用服务器进行注册的 过程对终端设备与 MME之间的第一类型的信令交互不受影响。 该实施方式 为后续进行小数据传输打下了基础。
其中, 另一种可选的注册流程如图 9B所示, 具体包括:
步骤 10a、终端设备向 MME发起附着请求消息, 该附着请求消息携带有 终端设备的 IMSI。
步骤 10b、 MME为终端设备执行 EPS附着流程, 该附着流程包括: 鉴权 和位置更新操作等, 但不创建默认承载 。
步骤 10c、 MME为终端设备分配 IP地址。
步骤 10d、 MME向终端设备发送附着接受消息, 该附着接受消息携带有 MME为该终端设备分配的 IP地址。
步骤 10e、 终端设备作为 IMS的用户代理(User Agent )根据本地存储的 终端设备的 IMSI和对应的 SIP标识生成第 ― SIP注册请求消息, 将第 ― SIP 注册请求消息封装在 NAS注册消息中发送给 MME。 该 NAS注册消息包括 MME为终端设备分配的 IP地址以及 MME的 IP地址。
上述 NAS注册消息是一种 SIP信令消息,相当于上述第一类型的第二信 令消息。
步骤 10f、 MME从 NAS注册消息中提取第一 SIP注册请求消息,将其封 装在注册消息中发送给 P-CSCF。
步骤 10g、 P-CSCF根据终端设备对应的 SIP标识, 确定该终端设备来自 于拜访网络, 是要进行注册的, 故向 DNS服务器发起对终端设备的归属网络 中的 I-CSCF地址的 DNS查询,然后根据 DNS查询结果,将注册( REGISTER ) 消息发送给 I-CSCF。
步骤 10h、 I-CSCF向 HSS发送 Cx查询。
步骤 10i、 HSS检查终端设备对应的用户的注册状态,根据签约数据确认 该用户是否允许注册, HSS返回 Cx查询响应, 即返回 S-CSCF需要的能力, I-CSCF根据 HSS返回的结果选择一个合适的 S-CSCF。
步骤 10j、 I-CSCF发送注册(REGISTER ) 消息给上述选择的 S-CSCF。 步骤 10k、 S-CSCF接收到注册(REGISTER ) 消息之后, 通过 Cx接口 向 HSS进行交互, 获取鉴权向量及用户签约信息等。
步骤 101、 S-CSCF将注册( REGISTER )消息发送给 AS,触发向 SCS/AS 的注册。
步骤 10m、 SCS/AS在接收到注册(REGISTER ) 消息后, 向 S-CSCF返 回 200 ok消息, 以完成注册。
上述注册消息为一种 SIP信令消息, 相当于上述第二类型的第二信令消 息。
步骤 10n、 S-CSCF向 P-CSCF返回 200 ok消息。
步骤 10o、 P-CSCF向 MME返回 200 ok消息。
上述 200 ok消息携带有第一 SIP注册完成消息, 是一种 SIP信令消息, 相当于上述第二类型的第三信令消息。
步骤 10p、 MME向终端设备发送 200 ok消息, 所述 200 ok消息包括第 一 SIP注册完成消息。
步骤 10p中的 200 ok消息是 SIP信令消息, 封装在 NAS信令消息中由
MME发送给终端设备, 相当于上述第一类型的第三信令消息。
在该实施方式中, 所述附着流程包括鉴权和位置更新操作等, 但不创建 默认承载, 即终端设备与 MME之间仅存在信令连接。 在该附着流程中, 由 MME给终端设备分配 IP地址, 终端设备上预先存储有终端设备对应的 SIP 标识, 终端设备自身作为用户代理(user agent ) 向应用服务器发起 SIP注册 流程, 通过将第一 SIP 注册请求消息封装在第一类型的信令消息中发送给 MME , 然后通过 MME与 P-CSCF之间的第二类型的信令消息传输给应用服 务器, 从而实现 SIP注册流程, 为后续终端设备与应用服务器进行数据传输 打下基础。
其中, 又一种可选的注册流程如图 9C所示, 具体包括:
步骤 1 la、 MME确定进行 IMS注册, 故发起 P-CSCF发现流程。
步骤 l lb、MME使用 MME对应的 SIP标识生成第二 SIP注册请求消息, 然后封装在注册(英文为 REGISTER )消息中发送给上述步骤发现的 P-CSCF, 即发起 SIP注册流程。 第二 SIP 注册请求消息包括 MME的标识和 MME对 应的 SIP标识。
步骤 1 lc、 P-CSCF根据 MME对应的 SIP标识, 确定该 MME来自于拜 访网络, 是要进行注册的, 故向 DNS服务器发起对 MME 的归属网络中的 I-CSCF地址的 DNS查询, 然后才艮据 DNS查询结果, 将注册( REGISTER ) 消息发送给 I-CSCF。
步骤 l ld、 I-CSCF向 HSS发送 Cx查询。
步骤 l le、 HSS检查 MME的注册状态,根据签约数据确认该 MME是否 允许注册, HSS返回 Cx查询响应, 即返回 S-CSCF需要的能力, I-CSCF根 据 HSS返回的结果选择一个合适的 S-CSCF。
步骤 l lf、 I-CSCF发送注册(REGISTER ) 消息给上述选择的 S-CSCF。 步骤 l lg、 S-CSCF接收到注册(REGISTER ) 消息之后, 通过 Cx接口 向 HSS进行交互, 获取鉴权向量及用户签约信息等。
步骤 l lh、 S-CSCF将注册(REGISTER )消息发送给 AS,触发向 SCS/AS 的注册。
步骤 l li、 SCS/AS在接收到注册(REGISTER ) 消息后, 向 S-CSCF返 回 200 ok消息, 以完成注册。
上述注册消息为一种 SIP信令消息, 相当于上述第二类型的第二信令消 息。
步骤 1 lj、 S-CSCF向 P-CSCF返回 200 ok消息。
步骤 1 lk、 P-CSCF向 MME返回 200 ok消息。
上述 200 ok消息携带有第一 SIP注册完成消息, 是一种 SIP信令消息, 相当于上述第二类型的第三信令消息。
可选的, 如图 9C所示, 步骤 I lk之后还包括:
步骤 111、 终端设备向 MME发起附着请求消息, 该附着请求消息携带有 终端设备的 IMSI。
步骤 l lm、 MME为终端设备执行 EPS附着流程, 该附着流程包括: 鉴 权和位置更新操作等, 但不创建默认承载。
步骤 1 ln、 MME向终端设备发送附着接受消息。
在步骤 111-步骤 l ln描述的附着流程中, 包括鉴权和位置更新操作等, 但不创建默认承载, 即终端设备与 MME之间仅存在信令连接。
在该实施方式中, MME作为用户代理(英文为 user agent ) 与 IMS系 统及 AS交互, 代替终端设备完成向应用服务器的注册流程, MME代替终端 设备向应用服务器进行注册的过程对终端设备与 MME之间的第一类型的信 令交互不受影响。 该实施方式为后续进行小数据传输打下了基础。
在一可选实施方式中, 所述小数据传输方法还包括: SCS/AS向终端设备 发送下行数据。具体的, S-CSCF从 HSS中查询路由信息,将数据发送至 MME, 由 MME通过 NAS信令消息发送给终端设备。
结合图 9C所示注册流程, 则下行数据传输过程如图 9D所示, 包括: 步骤 12a、 SCS/AS 发送信息 (MESSAGE ) 消息给 S-CSCF , 该信息 ( MESSAGE )消息携带有下行数据。 该下行数据携带有终端设备对应的 SIP 标识。
在 MME完成注册流程, 并且终端设备完成 EPS 附着流程后, SCS/AS 将发送给终端设备的下行数据封装在信息 ( MESSAGE )消息发送给 S-CSCF。
步骤 12b、 S-CSCF根据终端设备对应的 SIP标识查询 HSS,从 HSS上该 终端设备的 IMSI和终端设备对应的 SIP标识的映射关系中获取终端设备的标 识 ,进而从 HSS上终端设备的标识与 MME的地址的映射关系中 ,获取 MME 的地址。
步骤 12c、 S-CSCF根据查询结果, 将信息 (MESSAGE ) 消息和 MME 的地址发送给 P-CSCF。
步骤 12d、 P-CSCF根据 MME的地址, 将信息 (MESSAGE ) 消息转发 至 MME。 在该实施方式中, 上述信息(MESSAGE )消息为一种 SIP信令消息, 相 当于上述第二类型的第四信令消息。
步骤 12e、 MME根据终端设备对应的 SIP标识查询 HSS,从 HSS上终端 设备的 IMSI和终端设备对应的 SIP标识的映射关系中获取终端设备的 IMSI, 向终端设备发送寻呼消息, 寻呼消息携带小数据传输指示。
步骤 12f、 终端设备向 MME发送服务请求消息, 以建立信令连接。
步骤 12g、 终端设备与 MME、 HSS等完成鉴权流程。
步骤 12h、 MME从接收到的信息 (MESSAGE ) 消息中提取要发送的下 行数据, 将下行数据封装在下行 NSA传输消息中发送给终端设备。
步骤 12h中的下行 NSA传输消息是一种 NAS信令消息, 相当于上述第 一类型的第四信令消息。
步骤 12i、 终端设备将传输响应消息封装在上行 NAS 传输消息发送给
MME。
步骤 12j、 MME向 P-CSCF发送传输响应消息。
步骤 12k、 P-CSCF将传输响应消息发送给 S-CSCF。
步骤 121、 S-CSCF将传输响应消息发送给 SCS/AS。
步骤 12m、 如果规定时间内没有其他数据发送, 则基站译放与终端设备 之间的 RRC连接以及与 MME之间的 S1信令连接。
在上述实施例中, 终端设备与应用服务器之间的上行数据和下行数据均 通过 MME与 P-CSCF之间以及 MME与终端设备之间的信令消息进行传输, 使得不需要再为终端设备建立用户面 RAB, 节约了网络资源, 减轻了网络负 担, 还有利于提高数据传输速率。
进一步, 如果 MME与 P-CSCF之间通过 MSC服务器连接, 则 MME与 P-CSCF之间的交互均通过 MSC服务器实现。 下面以终端设备向 SCS/AS发 送上行数据为例进行说明, 关于 SCS/AS 向终端设备发送下行数据的过程, 本领域技术人员可以根据本发明相关实施例的记载很容易获知。 如图 10 所 示, 又一种小数据传输的流程包括:
步骤 13a、终端设备判断待发送的上行数据是否为小数据,在判断出待发 送的上行数据为小数据时, 决定通过信令的方式进行小数据发送。
步骤 13b、 终端设备向基站发送 RRC连接请求消息, 请求建立 RRC连 接, 该 RRC连接请求消息携带的信元 "建立原因值"指示基站仅为终端设备 建立信令连接。
步骤 13c、 基站向终端设备发送 RRC连接建立消息, 指示终端设备建立 RRC连接。
步骤 13d、 终端设备向基站发送 RRC连接完成消息, 该 RRC连接完成 消息携带 NAS PDU , 待发送上行数据封装在 NAS PDU中。
步骤 13e、 基站通过初始 UE消息将 NAS PDU发送给 MME。
步骤 13f、 终端设备通过基站与 MME、 HSS等进行鉴权和安全流程。 该过程属于现有技术, 在此不再赘述。
步骤 13g、MME从初始 UE消息中获取上行数据,将上行数据封装在 SGs 接口的上行数据发送消息中,通过与 MSC服务器之间的 SGs接口发送给 MSC 服务器。
步骤 13h、 MSC服务器从 SGs接口的上行数据发送消息中获取上行数据, 并将上行数据封装在信息 (英文为 MESSAGE ) 消息中发送给 P-CSCF。
步骤 13i、 P-CSCF转发信息 (MESSAGE ) 消息到 S-CSCF。
步骤 13j、 S-CSCF基于初始过滤准则,触发向 SCS/AS的信息( MESSAGE ) 消息传输。
步骤 13k、 S-CSCF发送确认 ( OK ) 消息给 P-CSCF。
步骤 131、 P-CSCF转发确认(OK ) 消息给 MSC服务器。
步骤 13m、 MSC服务器将确认 ( OK ) 消息封装在 SGs接口的下行数据 发送消息中, 通过 SGs接口发送给 MME。
步骤 13n、 MME通过下行 NAS传输消息发送确认消息给基站。
步骤 13o、 基站通过下行信息传输消息传送确认消息给终端设备。
步骤 13p、 如果规定时间内没有其他数据发送, 则基站译放与终端设备 之间的 RRC连接以及与 MME之间的 S 1信令连接。
由上述可见,通过利用现有 MSC服务器与 MME和 P-CSCF之间的互联, 可以减少对 MME的改动 , 使得 MME无需支持 SIP协议。
另外, 上述各实施例还具有以下有益效果: 可重用 IMS系统能力、 签约 及标识等, 解决 MTC终端的漫游、 计费等问题, 方便 MTC终端外部标识的 使用及与应用服务器的交互。 图 11为本发明一实施例提供的终端设备的结构示意图。 如图 11所示, 本实施例的终端设备包括: 判断模块 111、 第一发送模块 112和第一接收模 块 113。
其中, 判断模块 111 , 用于判断待发送上行数据的数据量是否小于预设 数据量门限。
第一发送模块 112, 与判断模块 111连接, 用于在判断模块 111判断出 上行数据的数据量小于预设数据量门限时, 向基站发送 RRC连接请求消息, 该 RRC连接请求消息包括指示基站仅为终端设备建立信令连接的指示信息。
第一接收模块 113 , 用于在第一发送模块 112发送 RRC连接请求消息之 后, 接收基站发送的 RRC连接建立消息。 可选的, 第一接收模块 113与第一 发送模块 112连接。
另外, 本实施例的第一发送模块 112还用于在第一接收模块 113接收到 RRC连接建立消息后, 将上行数据携带在 RRC连接完成消息中发送给基站, 以使基站根据指示信息, 将上行数据通过基站与 MME之间的第一类型的第 一信令消息发送给 MME , 以使 MME通过 MME与 P-CSCF之间的第二类型 的第一信令消息将上行数据发送给上行数据对应的应用服务器。
在本实施例的一可选实施方式中, 第一发送模块 112还用于在判断模块 111判断待发送上行数据的数据量是否小于预设数据量门限之前,向 MME发 送附着请求消息,以使 MME通过 MME与 P-CSCF之间的第二类型的第二信 令消息向应用服务器发送第一 SIP注册请求消息, 该附着请求消息包括终端 设备的标识, 第一 SIP注册请求消息包括终端设备的标识和终端设备对应的 SIP标识。
第一接收模块 113还用于在第一发送模块 112向 MME发送附着请求消 息后 , 接收 MME发送的附着接受消息 , 该附着接受消息是 MME通过 MME 与 P-CSCF之间的第二类型的第三信令消息接收到应用服务器返回的第一 SIP 注册完成消息后生成的, 第一 SIP注册完成消息是应用服务器在接收到终端 设备对应的 SIP标识后返回的。
在该实施方式中, 本实施例的终端设备通过第一发送模块 112和第一接 收模块 113在进行 EPS附着过程中, 实现由 MMS代替本实施例的终端设备 作为用户代理完成向应用服务器的 SIP注册流程。 其中, 本实施例的终端设 备与 MME之间仅存在信令连接。
在本实施例的一可选实施方式中, 第一发送模块 112还用于在判断模块 111判断待发送上行数据的数据量是否小于预设数据量门限之前,向 MME发 送附着请求消息, 该附着请求消息包括终端设备的标识, 以及用于在第一接 收模块 113接收到 MME发送的附着接受消息后,根据附着接受消息中 MME 为终端设备分配的 IP地址, 通过终端设备与 MME之间的第一类型的第二信 令消息向 MME发送第一 SIP注册请求消息 ,以使 MME通过 MME与 P-CSCF 之间的第二类型的第二信令消息, 将第一 SIP注册请求消息发送给应用服务 器,第一 SIP注册请求消息包括终端设备的标识和终端设备对应的 SIP标识;。
第一接收模块 113还用于在第一发送模块 112向 MME发送附着请求消 息后, 接收 MME发送的附着接受消息, 该附着接受消息包括 MME为终端 设备分配的 IP地址; 以及用于在第一发送模块 112向 MME发送第 ― SIP注 册请求消息之后, 通过终端设备与 MME之间的第一类型的第三信令消息, 接收 MME返回的第一 SIP注册完成消息, 其中, 第一 SIP注册完成消息是 应用服务器在接收到终端设备对应的 SIP标识后返回的 , MME是通过 MME 与 P-CSCF之间的第二类型的第三信令消息接收到第一 SIP注册完成消息的。
在该实施方式中, 本实施例的终端设备通过第一发送模块 112和第一接 收模块 113在 EPS附着过程中作为用户代理实现向应用服务器的 SIP注册流 程。 本实施例的终端设备与 MME之间仅存在信令连接。
在本实施例的一可选实施方式中, 第一发送模块 112还用于在判断模块
111判断待发送上行数据的数据量是否小于预设数据量门限之前,向 MME发 送附着请求消息, 该附着请求消息包括终端设备的标识。
第一接收模块 113还用于在第一发送模块 112向 MME发送附着请求消 息后, 接收 MME发送的附着接受消息。
在该实施方式中, 本实施例的终端设备通过第一发送模块 112和第一接 收模块 113完成了 EPS附着流程, 在 EPS附着过程中不建立默认承载, 即本 实施例的终端设备与 MME之间仅存在信令连接。 其中, MME直接作为用户 代理向应用服务器进行 SIP注册。
在本实施例的一可选实施方式中, 第一接收模块 113还用于接收 MME 发送的寻呼消息, 以及接收 MME根据第一发送模块 112发送的服务请求消 息发送的第一类型的第四信令消息。 其中, 寻呼消息是 MME通过 MME与 P-CSCF之间的第二类型的第四信令消息接收到应用服务器发送给终端设备 的下行数据后生成的, 第一类型的第四信令消息包括下行数据。
第一发送模块 112还用于在第一接收模块 113 接收到寻呼消息后, 向 MME发送服务请求消息,该服务请求消息用于指示 MME仅为终端设备建立 信令连接。
本实施例提供的终端设备的各功能模块, 可用于执行上述从终端设备角 度描述的数据传输方法的流程, 其具体工作原理不再赘述, 详见方法实施例 的描述。
本实施例的终端设备, 基于 MME与终端设备之间的第一类型的信令消 息和 MME与 P-CSCF之间的第二类型的信令消息进行小数据的传输, 无需 专门建立或恢复终端设备与网络空口侧的用户面 RAB, 节约了网络资源, 提 高了小数据的传输效率, 减少终端设备与网络侧的信令交互, 减少网络负荷。
图 12为本发明另一实施例提供的终端设备的结构示意图。如图 12所示, 本实施例的终端设备包括: 处理器 121、 发送器 122和接收器 123。
处理器 121 , 用于判断待发送上行数据的数据量是否小于预设数据量门 限。
发送器 122, 与处理器 121连接, 用于在处理器 121判断出上行数据的 数据量小于预设数据量门限时, 向基站发送 RRC连接请求消息, 该 RRC连 接请求消息包括指示基站仅为终端设备建立信令连接的指示信息。
接收器 123 , 用于在发送器 122发送 RRC连接请求消息之后, 接收基站 发送的 RRC连接建立消息。 可选的, 发送器 122与接收器 123连接。
发送器 122还用于在接收器 123接收到 RRC连接建立消息后,将上行数 据携带在 RRC连接完成消息中发送给基站, 以使基站根据指示信息, 将上行 数据通过基站与 MME之间的第一类型的第一信令消息发送给 MME, 以使 MME通过 MME与 P-CSCF之间的第二类型的第一信令消息将上行数据发送 给上行数据对应的应用服务器。
本实施例提供的终端设备可用于执行上述从终端设备角度描述的数据传 输方法的流程, 其具体工作原理不再赘述, 详见方法实施例的描述。
本实施例的终端设备, 基于 MME与终端设备之间的第一类型的信令消 息和 MME与 P-CSCF之间的第二类型的信令消息进行小数据的传输, 无需 专门建立或恢复终端设备与网络空口侧的用户面 RAB, 节约了网络资源, 提 高了小数据的传输效率, 减少终端设备与网络侧的信令交互, 减少网络负荷。
图 13为本发明一实施例提供的基站的结构示意图。 如图 13所示, 本实 施例的基站包括: 第二接收模块 131和第二发送模块 132。
第二接收模块 131 , 用于接收终端设备发送的 RRC连接请求消息, 以及 在第二发送模块 132向终端设备发送 RRC连接建立消息后,接收终端设备发 送的 RRC连接完成消息, 该 RRC连接请求消息是终端设备判断出待发送上 行数据的数据量小于预设数据量门限时生成的,该 RRC连接请求消息包括指 示基站仅为终端设备建立信令连接的指示信息,该 RRC连接完成消息包括上 行数据。 可选的, 第二接收模块 131和第二发送模块 132连接。
第二发送模块 132, 用于在第二接收模块 131接收到 RRC连接请求消息 后, 向终端设备发送 RRC连接建立消息, 以及在第二接收模块 131接收到 RRC连接完成消息后, 根据指示信息, 通过基站与 MME之间的第一类型的 第一信令消息将上行数据发送给 MME, 以使 MME通过 MME与 P-CSCF之
" ' ' 、 ' 、 、: 、 、:
本实施例提供的基站的各功能模块, 可用于执行上述从基站角度描述的 数据传输方法的流程, 其具体工作原理不再赘述, 详见方法实施例的描述。
本实施例的基站, 与上述实施例提供的终端设备相配合, 基于 MME与 终端设备之间的第一类型的信令消息和 MME与 P-CSCF之间的第二类型的 信令消息进行小数据的传输, 无需专门建立或恢复终端设备与网络空口侧的 用户面 RAB, 节约了网络资源, 提高了小数据的传输效率, 减少终端设备与 网络侧的信令交互, 减少网络负荷。
图 14为本发明另一实施例提供的基站的结构示意图。 如图 14所示, 本 实施例的基站包括: 接收器 141和发送器 142。
接收器 141 , 用于接收终端设备发送的 RRC连接请求消息, 以及在发送 器 142向终端设备发送 RRC连接建立消息后, 接收终端设备发送的 RRC连 接完成消息,该 RRC连接请求消息是终端设备判断出待发送上行数据的数据 量小于预设数据量门限时生成的,该 RRC连接请求消息包括指示基站仅为终 端设备建立信令连接的指示信息, 该 RRC连接完成消息包括上行数据。
发送器 142, 用于在接收器 141接收到 RRC连接请求消息后, 向终端设 备发送 RRC连接建立消息,以及在接收器 141接收到 RRC连接完成消息后, 根据指示信息, 通过基站与 MME之间的第一类型的第一信令消息将上行数 据发送给 MME, 以使 MME通过 MME与 P-CSCF之间的第二类型的第一信 令消息将上行数据发送给上行数据对应的应用服务器。
本实施例提供的基站可用于执行上述从基站角度描述的数据传输方法的 流程, 其具体工作原理不再赘述, 详见方法实施例的描述。
本实施例的基站, 与上述实施例提供的终端设备相配合, 基于 MME与 终端设备之间的第一类型的信令消息和 MME与 P-CSCF之间的第二类型的 信令消息进行小数据的传输, 无需专门建立或恢复终端设备与网络空口侧的 用户面 RAB, 节约了网络资源, 提高了小数据的传输效率, 减少终端设备与 网络侧的信令交互, 减少网络负荷。
图 15为本发明一实施例提供的 MME的结构示意图。 如图 15所示, 本 实施例的 MME包括: 第三接收模块 151和第三发送模块 152。
第三接收模块 151 , 用于接收基站发送的第一类型的第一信令消息, 第 一类型的第一信令消息是基站在接收到终端设备发送的 RRC 连接完成消息 后, 根据终端设备发送的 RRC连接请求消息中的指示信息生成的, 该 RRC 连接完成消息包括终端设备发送给应用服务器的上行数据, 该第一类型的第 一信令消息包括上行数据, 该指示信息用于指示基站仅为终端设备建立信令 连接。
第三发送模块 152,与第三接收模块 151连接,用于通过 MME与 P-CSCF 之间的第二类型的第一信令消息, 将第三接收模块 151接收到的上行数据发 送给应用服务器。
在本实施例的一可选实施方式中, 第三接收模块 151还用于在接收第一 类型的第一信令消息之前, 接收终端设备发送的附着请求消息, 以及在第三 发送模块 152 向应用服务器发送第一 SIP 注册请求消息后, 通过 MME与 P-CSCF之间的第二类型的第三信令消息,接收应用服务器在接收到终端设备 对应的 SIP标识后返回的第一 SIP注册完成消息, 该附着请求消息包括终端 设备的标识。 基于上述, 本实施例的 MME还包括: 获取模块 153。
获取模块 153 ,用于根据终端设备的标识,获取终端设备对应的 SIP标识, 并生成第一 SIP注册请求消息, 该第一 SIP注册请求消息包括终端设备的标 识和终端设备对应的 SIP标识。
可选的, 获取模块 153用于根据终端设备的标识, 获取终端设备对应的
SIP标识包括: 获取模块 153具体用于向 HSS发送位置更新请求消息, 该位 置更新请求消息包括终端设备的标识, 并接收 HSS根据终端设备的标识返回 的终端设备的标识和终端设备对应的 SIP标识之间的映射关系。 或者
获取模块 153具体用于根据终端设备的标识, 生成终端设备对应的 SIP 标识。 获取模块 153与第三接收模块 151连接, 用于向第三接收模块 151提 供终端设备对应的 SIP标识。
相应地, 第三发送模块 152还用于通过 MME与 P-CSCF之间的第二类 型的第二信令消息向应用服务器发送第一 SIP注册请求消息, 以及在第三接 收模块 151接收到第一 SIP注册完成消息后,向终端设备发送附着接受消息, 该附着接受消息包括第 ― SIP注册完成消息。
在该实施方式中,本实施例的 MME通过第三接收模块 151、第三发送模 块 152以及获取模块 153 , 在终端设备的 EPS附着流程中实现替代终端设备 完成向应用服务器的 SIP注册流程。 其中, 本实施例的 MME与终端设备之 间仅存在信令连接。
在本实施例的一可选实施方式中, 第三接收模块 151还用于在接收第一 类型的第一信令消息之前, 接收终端设备发送的附着请求消息, 以及在第三 发送模块 152向终端设备发送附着接受消息后, 接收终端设备根据 MME为 终端设备分配的 IP地址发送的第一类型的第二信令消息, 并在第三发送模块 152向应用服务器发送第一 SIP注册请求消息后,接收应用服务器在接收到终 端设备对应的 SIP标识后返回的第一 SIP注册完成消息; 该附着请求消息包 括终端设备的标识,该第一类型的第二信令消息包括第一 SIP注册请求消息, 该第一 SIP注册请求消息包括终端设备的标识和终端设备对应的 SIP标识。
基于上述, 本实施例的 MME还包括: 分配模块 154。 分配模块 154, 用 于为终端设备分配 IP地址。
相应地, 第三发送模块 152还用于在第三接收模块 151接收到附着请求 消息后, 向终端设备发送附着接受消息, 该附着接受消息包括上述 IP地址, 以及在第三接收模块 151接收到第一类型的第二信令消息后, 通过 MME与 P-CSCF之间的第二类型的第二信令消息,将第一 SIP注册请求消息发送给应 用服务器, 以及在第三接收模块 151接收到第一 SIP注册完成消息后, 向终 端设备发送第一类型的第三信令消息,第一类型的第三信令消息包括第一 SIP 注册完成消息。 可选的, 分配模块 154与第三发送模块 152连接, 用于向第 三发送模块 152提供 MME为终端设备分配的 IP地址。
在该实施方式中,本实施例的 MME通过第三接收模块 151、第三发送模 块 152以及分配模块 154, 完成终端设备的 EPS附着流程并使得终端设备完 成向应用服务器的 SIP注册流程。 其中, 本实施例的 MME与终端设备之间 仅存在信令连接。
在本实施例的一可选实施方式中, 第三发送模块 152还用于在第三接收 模块 151接收第一类型的第一信令消息之前, 通过 MME与 P-CSCF之间的 第二类型的第二信令消息, 向 P-CSCF 发送第二 SIP 注册请求消息, 以使 P-CSCF将第二 SIP注册请求消息发送给应用服务器,该第二类型的第二信令 消息包括第二 SIP注册请求消息, 该第二 SIP注册请求消息包括 MME的标 识和 MME对应的 SIP标识。
第三接收模块 151还用于在第三发送模块 152发送第二 SIP注册请求消 息后, 通过 MME与 P-CSCF之间的第二类型的第三信令消息, 接收应用服 务器在接收到 MME对应的 SIP标识后返回的第二 SIP注册完成消息。
基于上述,第三接收模块 151还用于在接收到第二 SIP注册完成消息后, 接收终端设备发送的附着请求消息, 该附着请求消息包括终端设备的标识。
第三发送模块 152还用于在第三接收模块 151接收到附着请求消息后, 向终端设备发送附着接受消息。
在该实施方式中, 本实施例的 MME通过第三接收模块 151和第三发送 模块 152完成终端设备的 EPS附着流程, 并通过第三接收模块 151和第三发 送模块 152作为用户代理完成向应用服务器的 SIP注册流程。 其中, 本实施 例的 MME与终端设备之间仅存在信令连接。
在本实施例的一可选实施方式中, 第三接收模块 151 还用于通过 MME 与 P-CSCF之间的第二类型的第四信令消息, 接收应用服务器发送给终端设 备的下行数据, 以及在第三发送模块 152向终端设备发送寻呼消息后, 接收 终端设备发送的服务请求消息。
第三发送模块 152还用于在第三接收模块 151接收到下行数据后, 向终 端设备发送寻呼消息, 以及在第三接收模块 151接收到服务请求消息后, 向 终端设备发送第一类型的第四信令消息, 第一类型的第四信令消息包括下行 数据。
在本实施例的一可选实施方式中, 第三发送模块 152用于通过 MME与 P-CSCF之间的第二类型的第一信令消息, 将上行数据发送给应用服务器包 括:
第三发送模块 152具体用于向 MSC服务器发送第三类型的第一信令消 息, 该第三类型的第一信令消息包括上行数据, 以使 MSC服务器将上行数据 封装在第二类型的第一信令消息中发送给 P-CSCF,以将上行数据发送给应用 服务器。
相应地, 第三接收模块 151用于通过 MME与 P-CSCF之间的第二类型 的第四信令消息, 接收应用服务器发送给终端设备的下行数据包括: 第三接 收模块 151具体用于接收 MSC服务器发送的第三类型的第二信令消息,第三 类型的第二信令消息是 MSC服务器根据 P-CSCF发送的第二类型的第四信令 消息生成的, 该第三类型的第二信令消息包括下行数据。
本实施例提供的 MME的各功能模块, 可用于执行上述从 MME角度描 述的数据传输方法的流程, 其具体工作原理不再赘述, 详见方法实施例的描 述。
本实施例的 MME, 与上述实施例提供的终端设备及基站相配合, 基于 MME与终端设备之间的第一类型的信令消息和 MME与 P-CSCF之间的第二 类型的信令消息进行小数据的传输, 无需专门建立或恢复终端设备与网络空 口侧的用户面 RAB, 节约了网络资源, 提高了小数据的传输效率, 减少终端 设备与网络侧的信令交互, 减少网络负荷。
图 16为本发明另一实施例提供的 MME的结构示意图。 如图 16所示, 本实施例的 MME包括: 接收器 161和发送器 162。
接收器 161 , 用于接收基站发送的第一类型的第一信令消息, 第一类型 的第一信令消息是基站在接收到终端设备发送的 RRC连接完成消息后,根据 终端设备发送的 RRC连接请求消息中的指示信息生成的, 该 RRC连接完成 消息包括终端设备发送给应用服务器的上行数据, 该第一类型的第一信令消 息包括上行数据, 该指示信息用于指示基站仅为终端设备建立信令连接。
发送器 162, 与接收器 161连接, 用于通过 MME与 P-CSCF之间的第二 类型的第一信令消息, 将接收器 161接收到的上行数据发送给应用服务器。
本实施例提供的 MME可用于执行上述从 MME角度描述的数据传输方 法的流程, 其具体工作原理不再赘述, 详见方法实施例的描述。
本实施例的 MME, 与上述实施例提供的终端设备及基站相配合, 基于 MME与终端设备之间的第一类型的信令消息和 MME与 P-CSCF之间的第二 类型的信令消息进行小数据的传输, 无需专门建立或恢复终端设备与网络空 口侧的用户面 RAB, 节约了网络资源, 提高了小数据的传输效率, 减少终端 设备与网络侧的信令交互, 减少网络负荷。
图 17为本发明一实施例提供的 P-CSCF的结构示意图。 如图 17所示, 本实施例的 P-CSCF包括: 第四接收模块 171和第四发送模块 172。
第四接收模块 171 ,用于通过 P-CSCF与 MME之间的第二类型的第一信 令消息, 接收终端设备发送给应用服务器的上行数据; 该第二类型的第一信 令消息是 MME接收到基站发送的第一类型的第一信令消息后, 根据第一类 型的第一信令消息中的上行数据生成的, 该第二类型的第一信令消息包括上 行数据, 该上行数据的数据量小于预设数据量门限。
第四发送模块 172, 与第四接收模块 171连接, 用于将第四接收模块 171 接收到的上行数据发送给 S-CSCF, 以使 S-CSCF将上行数据发送给应用服务 器。
在本实施例的一可选实施方式中, 第四接收模块 171还用于在接收上行 数据之前,通过 P-CSCF与 MME之间的第二类型的第二信令消息,接收 MME 发送的第一 SIP注册请求消息, 并在第四发送模块将第一 SIP注册请求消息 发送给应用服务器后, 接收 S-CSCF发送的应用服务器在接收到终端设备对 应的 SIP标识返回的第一 SIP注册完成消息, 第一 SIP注册请求消息包括终 端设备的标识和终端设备对应的 SIP标识。
第四发送模块 172还用于在第四接收模块 171接收到第一 SIP注册请求 消息后, 将第一 SIP注册请求消息发送给 S-CSCF, 以使 S-CSCF将第一 SIP 注册请求消息发送给应用服务器, 以及在第四接收模块 171接收到第一 SIP 注册完成消息后, 通过 P-CSCF与 MME之间的第二类型的第三信令消息, 向 MME发送第一 SIP注册完成消息。
在本实施例的一可选实施方式中, 第四接收模块 171还用于在接收上行 数据之前,通过 P-CSCF与 MME之间的第二类型的第二信令消息,接收 MME 发送的第二 SIP注册请求消息, 以及在第四发送模块 172将第二 SIP注册请 求消息发送给 S-CSCF后,接收 S-CSCF发送的应用服务器在接收到 MME对 应的 SIP标识后返回的第二 SIP注册完成消息, 该第二 SIP注册请求消息包 括 MME的标识和 MME对应的 SIP标识。
第四发送模块 172还用于在第四接收模块 171接收到第二 SIP注册请求 消息后, 将第二 SIP注册请求消息发送给 S-CSCF , 以使 S-CSCF将第二 SIP 注册请求消息发送给应用服务器, 以及在第四接收模块 171接收到第二 SIP 注册完成消息后, 通过 P-CSCF与 MME之间的第二类型的第三信令消息, 向 MME发送第二 SIP注册完成消息。
在本实施例的一可选实施方式中,第四接收模块 171还用于接收 S-CSCF 发送的应用服务器发送给终端设备的下行数据和 MME的地址信息, MME的 地址信息是 S-CSCF根据终端设备对应的 SIP标识查询 HSS获取的, HSS存 储有终端设备的标识与终端设备对应的 SIP标识之间的映射关系, 以及终端 设备的标识与 MME的地址信息之间的映射关系。
第四发送模块 172还用于在第四接收模块 171接收到下行数据和 MME 的地址信息后,根据 MME的地址信息,通过 P-CSCF与 MME之间的第二类 型的第四信令消息, 向 MME发送下行数据。
在本实施例的一可选实施方式中, 第四接收模块 171 用于通过 P-CSCF 与 MME之间的第二信令消息, 接收终端设备发送给应用服务器的上行数据 包括:第四接收模块 171具体用于接收 MSC服务器发送的第二类型的第一信 令消息,第二类型的第一信令消息是 MSC服务器根据 MME发送的第三类型 的第一信令消息生成的, 该第三类型的第一信令消息包括上行数据。
在本实施例的一可选实施方式中, 第四发送模块 172用于根据 MME的 地址信息 , 通过 P-CSCF与 MME之间的第二类型的第四信令消息 , 向 MME 发送下行数据包括: 第四发送模块 172具体用于向 MSC服务器发送的第二类型的第四信令消 息,以使 MSC服务器将第二类型的第四信令消息中的下行数据封装在第三类 型的第二信令消息中发送给 MME。
本实施例提供的 P-CSCF的各功能模块,可用于执行上述从 P-CSCF角度 描述的数据传输方法的流程, 其具体工作原理不再赘述, 详见方法实施例的 描述。
本实施例的 P-CSCF, 与上述实施例提供的终端设备、基站及 MME相配 合,基于 MME与终端设备之间的第一类型的信令消息和 MME与 P-CSCF之 间的第二类型的信令消息进行小数据的传输, 无需专门建立或恢复终端设备 与网络空口侧的用户面 RAB, 节约了网络资源, 提高了小数据的传输效率, 减少终端设备与网络侧的信令交互, 减少网络负荷。
图 18为本发明另一实施例提供的 P-CSCF的结构示意图。 如图 18所示, 本实施例的 P-CSCF包括: 接收器 181和发送器 182。
其中, 接收器 181 , 用于通过 P-CSCF与 MME之间的第二类型的第一信 令消息, 接收终端设备发送给应用服务器的上行数据; 该第二类型的第一信 令消息是 MME接收到基站发送的第一类型的第一信令消息后, 根据第一类 型的第一信令消息中的上行数据生成的, 该第二类型的第一信令消息包括上 行数据, 该上行数据的数据量小于预设数据量门限。
发送器 182, 与接收器 181连接, 用于将接收器 181接收到的上行数据 发送给 S-CSCF, 以使 S-CSCF将上行数据发送给应用服务器。 方法的流程, 其具体工作原理不再赘述, 详见方法实施例的描述。
本实施例的 P-CSCF, 与上述实施例提供的终端设备、基站及 MME相配 合,基于 MME与终端设备之间的第一类型的信令消息和 MME与 P-CSCF之 间的第二类型的信令消息进行小数据的传输, 无需专门建立或恢复终端设备 与网络空口侧的用户面 RAB, 节约了网络资源, 提高了小数据的传输效率, 减少终端设备与网络侧的信令交互, 减少网络负荷。
本发明一实施例提供一种数据传输系统, 包括: 本发明上述实施例提供 的终端设备、 基站、 MME和 P-CSCF, 其中, P-CSCF与 MME连接。 终端设 备、 基站、 MME和 P-CSCF的结构和工作原理不再赘述, 可参见上述实施例 的描述。
本实施例提供的数据传输系统可用于执行上述各数据传输方法实施例的 流程, 同样可基于 MME与终端设备之间的第一类型的信令消息和 MME与 P-CSCF之间的第二类型的信令消息进行小数据的传输,无需专门建立或恢复 终端设备与网络空口侧的用户面 RAB, 节约了网络资源, 提高了小数据的传 输效率, 减少终端设备与网络侧的信令交互, 减少网络负荷。
本领域普通技术人员可以理解: 实现上述方法实施例的全部或部分步骤 可以通过程序指令相关的硬件来完成, 前述的程序可以存储于一计算机可读 取存储介质中, 该程序在执行时, 执行包括上述方法实施例的步骤; 而前述 的存储介质包括: ROM, RAM, 磁碟或者光盘等各种可以存储程序代码的介 质。
最后应说明的是: 以上各实施例仅用以说明本发明的技术方案, 而非对 其限制; 尽管参照前述各实施例对本发明进行了详细的说明, 本领域的普通 技术人员应当理解:其依然可以对前述各实施例所记载的技术方案进行修改, 或者对其中部分或者全部技术特征进行等同替换; 而这些修改或者替换, 并 不使相应技术方案的本质脱离本发明各实施例技术方案的范围。

Claims

权 利 要求 书
1、 一种数据传输方法, 其特征在于, 包括:
终端设备判断待发送上行数据的数据量是否小于预设数据量门限; 当所述上行数据的数据量小于所述预设数据量门限时, 所述终端设备向 基站发送无线资源控制 RRC连接请求消息, 所述 RRC连接请求消息包括指 示所述基站仅为所述终端设备建立信令连接的指示信息;
所述终端设备接收所述基站发送的 RRC连接建立消息;
所述终端设备将所述上行数据携带在 RRC 连接完成消息中发送给所述 基站, 以使所述基站根据所述指示信息, 将所述上行数据通过所述基站与移 动性管理实体 MME之间的第一类型的第一信令消息发送给所述 MME,以使 所述 MME通过所述 MME与代理呼叫会话控制功能 P-CSCF之间的第二类型
2、 根据权利要求 1所述的数据传输方法, 其特征在于, 所述终端设备判 断待发送上行数据的数据量是否小于预设数据量门限之前包括:
所述终端设备向所述 MME发送附着请求消息, 以使所述 MME通过所 述 MME与所述 P-CSCF之间的第二类型的第二信令消息向所述应用服务器 发送第一会话初始协议 SIP注册请求消息, 所述附着请求消息包括所述终端 设备的标识, 所述第一 SIP注册请求消息包括所述终端设备的标识和所述终 端设备对应的 SIP标识;
所述终端设备接收所述 MME发送的附着接受消息, 所述附着接受消息 是所述 MME通过所述 MME与所述 P-CSCF之间的第二类型的第三信令消息 接收到所述应用服务器返回的第一 SIP注册完成消息后生成的,所述第一 SIP 注册完成消息是所述应用服务器在接收到所述终端设备对应的 SIP标识后返 回的;
其中, 所述终端设备与所述 MME之间仅存在信令连接。
3、 根据权利要求 1所述的数据传输方法, 其特征在于, 所述终端设备判 断待发送上行数据的数据量是否小于预设数据量门限之前包括:
所述终端设备向所述 MME发送附着请求消息, 所述附着请求消息包括 所述终端设备的标识;
所述终端设备接收所述 MME发送的附着接受消息, 所述附着接受消息 包括所述 MME为所述终端设备分配的 IP地址;
所述终端设备根据所述 IP地址, 通过所述终端设备与所述 MME之间的 第一类型的第二信令消息向所述 MME发送第一 SIP注册请求消息, 以使所 述 MME通过所述 MME与所述 P-CSCF之间的第二类型的第二信令消息,将 所述第一 SIP注册请求消息发送给所述应用服务器, 所述第一 SIP注册请求 消息包括所述终端设备的标识和所述终端设备对应的 SIP标识;
所述终端设备通过所述终端设备与所述 MME之间的第一类型的第三信 令消息, 接收所述 MME返回的第一 SIP注册完成消息, 所述第一 SIP注册 完成消息是所述应用服务器在接收到所述终端设备对应的 SIP标识后返回的, 所述 MME是通过所述 MME与所述 P-CSCF之间的第二类型的第三信令消息 接收到所述第一 SIP注册完成消息的;
其中, 所述终端设备与所述 MME之间仅存在信令连接。
4、 根据权利要求 1所述的数据传输方法, 其特征在于, 所述终端设备判 断待发送上行数据的数据量是否小于预设数据量门限之前包括:
所述终端设备向所述 MME发送附着请求消息, 所述附着请求消息包括 所述终端设备的标识;
所述终端设备接收所述 MME发送的附着接受消息;
其中, 所述终端设备与所述 MME之间仅存在信令连接。
5、根据权利要求 1-4任一项所述的数据传输方法, 其特征在于,还包括: 所述终端设备接收所述 MME发送的寻呼消息, 所述寻呼消息是所述
MME通过所述 MME与所述 P-CSCF之间的第二类型的第四信令消息在接收 到所述应用服务器发送给所述终端设备的下行数据后生成的;
所述终端设备根据所述寻呼消息, 向所述 MME发送服务请求消息, 所 述服务请求消息用于指示所述 MME仅为所述终端设备建立信令连接;
所述终端设备接收所述 MME根据所述服务请求消息发送的第一类型的 第四信令消息, 所述第一类型的第四信令消息包括所述下行数据。
6、 一种数据传输方法, 其特征在于, 包括:
基站接收终端设备发送的无线资源控制 RRC连接请求消息, 所述 RRC 连接请求消息是所述终端设备判断出待发送上行数据的数据量小于预设数据 量门限时生成的,所述 RRC连接请求消息包括指示所述基站仅为所述终端设 备建立信令连接的指示信息;
所述基站向所述终端设备发送 RRC连接建立消息;
所述基站接收所述终端设备发送的 RRC连接完成消息, 所述 RRC连接 完成消息包括所述上行数据;
所述基站根据所述指示信息, 通过所述基站与移动性管理实体 MME之 间的第一类型的第一信令消息将所述上行数据发送给所述 MME, 以使所述 MME通过所述 MME与代理呼叫会话控制功能 P-CSCF之间的第二类型的第
7、 一种数据传输方法, 其特征在于, 包括:
移动性管理实体 MME接收基站发送的第一类型的第一信令消息, 所述 第一类型的第一信令消息是所述基站在接收到终端设备发送的无线资源控制 RRC连接完成消息后, 根据所述终端设备发送的 RRC连接请求消息中的指 示信息生成的,所述 RRC连接完成消息包括所述终端设备发送给应用服务器 的上行数据, 所述第一类型的第一信令消息包括所述上行数据, 所述指示信 息用于指示所述基站仅为所述终端设备建立信令连接;
所述 MME通过所述 MME与代理呼叫会话控制功能 P-CSCF之间的第二 类型的第一信令消息, 将所述上行数据发送给所述应用服务器。
8、 根据权利要求 7所述的数据传输方法, 其特征在于, 所述移动性管理 实体 MME接收基站发送的第一类型的第一信令消息之前包括:
所述 MME接收所述终端设备发送的附着请求消息, 所述附着请求消息 包括所述终端设备的标识;
所述 MME根据所述终端设备的标识, 获取所述终端设备对应的会话初 始协议 SIP标识, 并生成第一 SIP注册请求消息, 所述第一 SIP注册请求消 息包括所述终端设备的标识和所述终端设备对应的 SIP标识;
所述 MME通过所述 MME与所述 P-CSCF之间的第二类型的第二信令消 息向所述应用服务器发送所述第一 SIP注册请求消息;
所述 MME通过所述 MME与所述 P-CSCF之间的第二类型的第三信令消 息, 接收所述应用服务器在接收到所述终端设备对应的 SIP标识后返回的第 一 SIP注册完成消息;
所述 MME向所述终端设备发送附着接受消息, 所述附着接受消息包括 所述第一 SIP注册完成消息;
其中, 所述终端设备与所述 MME之间仅存在信令连接。
9、 根据权利要求 8所述的数据传输方法, 其特征在于, 所述 MME根据 所述终端设备的标识, 获取所述终端设备对应的 SIP标识包括:
所述 MME向位置归属服务器 HSS发送位置更新请求消息, 所述位置更 新请求消息包括所述终端设备的标识;
所述 MME接收所述 HSS根据所述终端设备的标识返回的所述终端设备 的标识和所述终端设备对应的 SIP标识之间的映射关系; 或者
所述 MME根据所述终端设备的标识, 生成所述终端设备对应的 SIP标 识。
10、 根据权利要求 7所述的数据传输方法, 其特征在于, 所述移动性管 理实体 MME接收基站发送的第一类型的第一信令消息之前包括:
所述 MME接收所述终端设备发送的附着请求消息, 所述附着请求消息 包括所述终端设备的标识;
所述 MME为所述终端设备分配 IP地址;
所述 MME向所述终端设备发送附着接受消息, 所述附着接受消息包括 所述 IP地址;
所述 MME接收所述终端设备根据所述 IP地址发送的第一类型的第二信 令消息, 所述第一类型的第二信令消息包括第一 SIP注册请求消息, 所述第 一 SIP注册请求消息包括所述终端设备的标识和所述终端设备对应的 SIP标 识;
所述 MME通过所述 MME与所述 P-CSCF之间的第二类型的第二信令消 息, 将所述第一 SIP注册请求消息发送给所述应用服务器;
所述 MME通过所述 MME与所述 P-CSCF之间的第二类型的第三信令消 息, 接收所述应用服务器在接收到所述终端设备对应的 SIP标识返回的第一 SIP注册完成消息;
所述 MME向所述终端设备发送第一类型的第三信令消息, 所述第一类 型的第三信令消息包括所述第一 SIP注册完成消息;
其中, 所述终端设备与所述 MME之间仅存在信令连接。
11、 根据权利要求 7所述的数据传输方法, 其特征在于, 所述移动性管 理实体 MME接收基站发送的第一类型的第一信令消息之前包括: 所述 MME通过所述 MME与所述 P-CSCF之间的第二类型的第二信令消 息, 向所述 P-CSCF发送第二 SIP注册请求消息, 以使所述 P-CSCF将所述第 二 SIP注册请求消息发送给所述应用服务器, 所述第二类型的第二信令消息 包括所述第二 SIP注册请求消息,所述第二 SIP注册请求消息包括所述 MME 的标识和所述 MME对应的 SIP标识;
所述 MME通过所述 MME与所述 P-CSCF之间的第二类型的第三信令消 息, 接收所述应用服务器在接收到所述 MME对应的 SIP标识后返回的第二
SIP注册完成消息。
12、 根据权利要求 11所述的数据传输方法, 其特征在于, 所述 MME通 过所述 MME与所述 P-CSCF之间的第二类型的第三信令消息, 接收所述应 用服务器在接收到所述 MME对应的 SIP标识后返回的第二 SIP注册完成消 息之后包括:
所述 MME接收所述终端设备发送的附着请求消息, 所述附着请求消息 包括所述终端设备的标识;
所述 MME向所述终端设备发送附着接受消息;
其中, 所述终端设备与所述 MME之间仅存在信令连接。
13、 根据权利要求 7-12任一项所述的数据传输方法, 其特征在于, 还包 括:
所述 MME通过所述 MME与所述 P-CSCF之间的第二类型的第四信令消 息, 接收所述应用服务器发送给所述终端设备的下行数据;
所述 MME向所述终端设备发送寻呼消息;
所述 MME接收所述终端设备发送的服务请求消息;
所述 MME向所述终端设备发送第一类型的第四信令消息, 所述第一类 型的第四信令消息包括所述下行数据。
14、 根据权利要求 7-12任一项所述的数据传输方法, 其特征在于, 所述 MME通过所述 MME与代理呼叫会话控制功能 P-CSCF之间的第二类型的第 一信令消息, 将所述上行数据发送给所述应用服务器包括:
所述 MME向 MSC服务器发送第三类型的第一信令消息,所述第三类型 的第一信令消息包括所述上行数据,以使所述 MSC服务器将所述上行数据封 装在所述第二类型的第一信令消息中发送给所述 P-CSCF,以将所述上行数据 发送给所述应用服务器。
15、 根据权利要求 13所述的数据传输方法, 其特征在于, 所述 MME通 过所述 MME与所述 P-CSCF之间的第二类型的第四信令消息, 接收所述应 用服务器发送给所述终端设备的下行数据包括:
所述 MME接收 MSC服务器发送的第三类型的第二信令消息,所述第三 类型的第二信令消息是所述 MSC服务器根据所述 P-CSCF发送的所述第二类 型的第四信令消息生成的,所述第三类型的第二信令消息包括所述下行数据。
16、 一种数据传输方法, 其特征在于, 包括:
代理呼叫会话控制功能 P-CSCF 通过所述 P-CSCF 与移动性管理实体
MME之间的第二类型的第一信令消息,接收终端设备发送给应用服务器的上 行数据; 所述第二类型的第一信令消息是所述 MME接收到基站发送的第一 类型的第一信令消息后, 根据所述第一类型的第一信令消息中的所述上行数 据生成的, 所述第二类型的第一信令消息包括所述上行数据, 所述上行数据 的数据量小于预设数据量门限;
所述 P-CSCF将所述上行数据发送给 S-CSCF, 以使所述 S-CSCF将所述 上行数据发送给所述应用服务器。
17、 根据权利要求 16所述的数据传输方法, 其特征在于, 所述代理呼叫 会话控制功能 P-CSCF通过所述 P-CSCF与移动性管理实体 MME之间的第二 类型的第一信令消息,接收终端设备发送给应用服务器的上行数据之前包括: 所述 P-CSCF通过所述 P-CSCF与所述 MME之间的第二类型的第二信令 消息, 接收所述 MME发送的第一 SIP注册请求消息, 所述第一 SIP注册请 求消息包括所述终端设备的标识和所述终端设备对应的 SIP标识;
所述 P-CSCF将所述第一 SIP注册请求消息发送给所述 S-CSCF, 以使所 述 S-CSCF将所述第一 SIP注册请求消息发送给所述应用服务器;
所述 P-CSCF接收所述 S-CSCF发送的所述应用服务器在接收到所述终端 设备对应的 SIP标识返回的第一 SIP注册完成消息;
所述 P-CSCF通过所述 P-CSCF与所述 MME之间的第二类型的第三信令 消息, 向所述 MME发送所述第一 SIP注册完成消息。
18、 根据权利要求 16所述的数据传输方法, 其特征在于, 所述代理呼叫 会话控制功能 P-CSCF通过所述 P-CSCF与移动性管理实体 MME之间的第二 类型的第一信令消息 ,接收终端设备发送给应用服务器的上行数据之前包括: 所述 P-CSCF通过所述 P-CSCF与所述 MME之间的第二类型的第二信令 消息, 接收所述 MME发送的第二 SIP注册请求消息, 所述第二 SIP注册请 求消息包括所述 MME的标识和所述 MME对应的 SIP标识;
所述 P-CSCF将所述第二 SIP注册请求消息发送给所述 S-CSCF, 以使所 述 S-CSCF将所述第二 SIP注册请求消息发送给所述应用服务器;
所述 P-CSCF接收所述 S-CSCF 发送的所述应用服务器在接收到所述 MME对应的 SIP标识后返回的第二 SIP注册完成消息;
所述 P-CSCF通过所述 P-CSCF与所述 MME之间的第二类型的第三信令 消息, 向所述 MME发送所述第二 SIP注册完成消息。
19、 根据权利要求 18所述的数据传输方法, 其特征在于, 还包括: 所述 P-CSCF接收所述 S-CSCF发送的所述应用服务器发送给终端设备的 下行数据和所述 MME的地址信息,所述 MME的地址信息是所述 S-CSCF根 据所述终端设备对应的 SIP标识查询归属存储服务器 HSS获取的, 所述 HSS 存储有所述终端设备的标识与所述终端设备对应的 SIP标识之间的映射关系, 以及所述终端设备的标识与所述 MME的地址信息之间的映射关系;
所述 P-CSCF根据所述 MME的地址信息 ,通过所述 P-CSCF与所述 MME 之间的第二类型的第四信令消息, 向所述 MME发送所述下行数据。
20、 根据权利要求 16-18任一项所述的数据传输方法, 其特征在于, 所 述代理呼叫会话控制功能 P-CSCF通过所述 P-CSCF与移动性管理实体 MME 之间的第二类型的第一信令消息, 接收终端设备发送给应用服务器的上行数 据包括:
所述 P-CSCF接收 MSC服务器发送的所述第二信令消息,所述第二信令 消息是所述 MSC服务器根据所述 MME发送的第三类型的第一信令消息生成 的, 所述第三类型的第一信令消息包括所述上行数据。
21、 根据权利要求 19所述的数据传输方法, 其特征在于, 所述 P-CSCF 根据所述 MME的地址信息,通过所述 P-CSCF与所述 MME之间的第二类型 的第四信令消息, 向所述 MME发送所述下行数据包括:
所述 P-CSCF向 MSC服务器发送的所述第二类型的第四信令消息, 以使 所述 MSC服务器将所述第二类型的第四信令消息中的所述下行数据封装在 第三类型的第二信令消息中发送给所述 MME。
22、 一种终端设备, 其特征在于, 包括:
判断模块,用于判断待发送上行数据的数据量是否小于预设数据量门限; 第一发送模块, 用于在所述判断模块判断出所述上行数据的数据量小于 所述预设数据量门限时, 向基站发送无线资源控制 RRC连接请求消息, 所述 RRC连接请求消息包括指示所述基站仅为所述终端设备建立信令连接的指示 信息;
第一接收模块,用于在所述第一发送模块发送所述 RRC连接请求消息之 后, 接收所述基站发送的 RRC连接建立消息;
所述第一发送模块还用于在所述第一接收模块接收到所述 RRC 连接建 立消息后, 将所述上行数据携带在 RRC连接完成消息中发送给所述基站, 以 使所述基站根据所述指示信息, 将所述上行数据通过所述基站与移动性管理 实体 MME之间的第一类型的第一信令消息发送给所述 MME ,以使所述 MME 通过所述 MME与代理呼叫会话控制功能 P-CSCF之间的第二类型的第一信
23、 根据权利要求 22所述的终端设备, 其特征在于, 所述第一发送模块 还用于在所述判断模块判断待发送上行数据的数据量是否小于预设数据量门 限之前, 向所述 MME发送附着请求消息, 以使所述 MME通过所述 MME 与所述 P-CSCF之间的第二类型的第二信令消息向所述应用服务器发送第一 会话初始协议 SIP注册请求消息, 所述附着请求消息包括所述终端设备的标 识, 所述第一 SIP注册请求消息包括所述终端设备的标识和所述终端设备对 应的 SIP标识;
所述第一接收模块还用于在所述第一发送模块向所述 MME发送所述附 着请求消息后, 接收所述 MME发送的附着接受消息, 所述附着接受消息是 所述 MME通过所述 MME与所述 P-CSCF之间的第二类型的第三信令消息接 收到所述应用服务器返回的第一 SIP注册完成消息后生成的, 所述第一 SIP 注册完成消息是所述应用服务器在接收到所述终端设备对应的 SIP标识后返 回的;
其中, 所述终端设备与所述 MME之间仅存在信令连接。
24、 根据权利要求 22所述的终端设备, 其特征在于, 所述第一发送模块 还用于在所述判断模块判断待发送上行数据的数据量是否小于预设数据量门 限之前, 向所述 MME发送附着请求消息, 所述附着请求消息包括所述终端 设备的标识; 以及用于在所述第一接收模块接收到所述 MME发送的附着接 受消息后, 根据所述附着接受消息中所述 MME为所述终端设备分配的 IP地 址, 通过所述终端设备与所述 MME之间的第一类型的第二信令消息向所述 MME发送第一 SIP注册请求消息, 以使所述 MME通过所述 MME与所述 P-CSCF之间的第二类型的第二信令消息,将所述第一 SIP注册请求消息发送 给所述应用服务器, 所述第一 SIP注册请求消息包括所述终端设备的标识和 所述终端设备对应的 SIP标识;
所述第一接收模块还用于在所述第一发送模块向所述 MME发送所述附 着请求消息后, 接收所述 MME发送的所述附着接受消息, 所述附着接受消 息包括所述 MME为所述终端设备分配的 IP地址; 以及用于在所述第一发送 模块向所述 MME发送所述第一 SIP注册请求消息之后, 通过所述终端设备 与所述 MME之间的第一类型的第三信令消息, 接收所述 MME返回的第一 SIP注册完成消息,所述第一 SIP注册完成消息是所述应用服务器在接收到所 述终端设备对应的 SIP标识后返回的, 所述 MME是通过所述 MME与所述 P-CSCF之间的第二类型的第三信令消息接收到所述第一 SIP 注册完成消息 的;
其中, 所述终端设备与所述 MME之间仅存在信令连接。
25、 根据权利要求 22所述的终端设备, 其特征在于, 所述第一发送模块 还用于在所述判断模块判断待发送上行数据的数据量是否小于预设数据量门 限之前, 向所述 MME发送附着请求消息, 所述附着请求消息包括所述终端 设备的标识;
所述第一接收模块还用于在所述第一发送模块向所述 MME发送所述附 着请求消息后, 接收所述 MME发送的附着接受消息;
其中, 所述终端设备与所述 MME之间仅存在信令连接。
26、 根据权利要求 22-25任一项所述的终端设备, 其特征在于, 所述第 一接收模块还用于接收所述 MME发送的寻呼消息, 以及接收所述 MME根 据所述第一发送模块发送的服务请求消息发送的第一类型的第四信令消息, 所述寻呼消息是所述 MME通过所述 MME与所述 P-CSCF之间的第二类型的 第四信令消息接收到所述应用服务器发送给所述终端设备的下行数据后生成 的, 所述第一类型的第四信令消息包括所述下行数据;
所述第一发送模块还用于在所述第一接收模块接收到所述寻呼消息后, 向所述 MME发送服务请求消息, 所述服务请求消息用于指示所述 MME仅 为所述终端设备建立信令连接。
27、 一种终端设备, 其特征在于, 包括:
处理器, 用于判断待发送上行数据的数据量是否小于预设数据量门限; 发送器, 用于在所述处理器判断出所述上行数据的数据量小于所述预设 数据量门限时, 向基站发送无线资源控制 RRC连接请求消息, 所述 RRC连 接请求消息包括指示所述基站仅为所述终端设备建立信令连接的指示信息; 接收器, 用于在所述发送器发送所述 RRC连接请求消息之后, 接收所述 基站发送的 RRC连接建立消息;
所述发送器还用于在所述接收器接收到所述 RRC连接建立消息后 ,将所 述上行数据携带在 RRC连接完成消息中发送给所述基站,以使所述基站根据 所述指示信息, 将所述上行数据通过所述基站与移动性管理实体 MME之间 的第一类型的第一信令消息发送给所述 MME ,以使所述 MME通过所述 MME 与代理呼叫会话控制功能 P-CSCF之间的第二类型的第一信令消息将所述上 行数据发送给所述上行数据对应的应用服务器。
28、 一种基站, 其特征在于, 包括:
第二接收模块,用于接收终端设备发送的无线资源控制 RRC连接请求消 息, 以及在第二发送模块向所述终端设备发送 RRC连接建立消息后, 接收所 述终端设备发送的 RRC连接完成消息, 所述 RRC连接请求消息是所述终端 设备判断出待发送上行数据的数据量小于预设数据量门限时生成的, 所述 RRC连接请求消息包括指示所述基站仅为所述终端设备建立信令连接的指示 信息, 所述 RRC连接完成消息包括所述上行数据;
所述第二发送模块,用于在所述第二接收模块接收到所述 RRC连接请求 消息后, 向所述终端设备发送所述 RRC连接建立消息, 以及在所述第二接收 模块接收到所述 RRC连接完成消息后, 根据所述指示信息, 通过所述基站与 移动性管理实体 MME之间的第一类型的第一信令消息将所述上行数据发送 给所述 MME, 以使所述 MME 通过所述 MME 与代理呼叫会话控制功能 P-CSCF之间的第二类型的第一信令消息将所述上行数据发送给所述上行数 据对应的应用服务器。
29、 一种基站, 其特征在于, 包括: 接收器和发送器;
所述接收器, 用于接收终端设备发送的无线资源控制 RRC 连接请求消 息, 以及在所述发送器向所述终端设备发送 RRC连接建立消息后,接收所述 终端设备发送的 RRC连接完成消息, 所述 RRC连接请求消息是所述终端设 备判断出待发送上行数据的数据量小于预设数据量门限时生成的, 所述 RRC 连接请求消息包括指示所述基站仅为所述终端设备建立信令连接的指示信 息, 所述 RRC连接完成消息包括所述上行数据;
所述发送器, 用于在所述接收器接收到所述 RRC连接请求消息后, 向所 述终端设备发送所述 RRC连接建立消息,以及在所述接收器接收到所述 RRC 连接完成消息后,根据所述指示信息,通过所述基站与移动性管理实体 MME 之间的第一类型的第一信令消息将所述上行数据发送给所述 MME,以使所述 MME通过所述 MME与代理呼叫会话控制功能 P-CSCF之间的第二类型的第
30、 一种移动性管理实体 MME, 其特征在于, 包括:
第三接收模块, 用于接收基站发送的第一类型的第一信令消息, 所述第 一类型的第一信令消息是所述基站在接收到终端设备发送的无线资源控制 RRC连接完成消息后, 根据所述终端设备发送的 RRC连接请求消息中的指 示信息生成的,所述 RRC连接完成消息包括所述终端设备发送给应用服务器 的上行数据, 所述第一类型的第一信令消息包括所述上行数据, 所述指示信 息用于指示所述基站仅为所述终端设备建立信令连接;
第三发送模块, 用于通过所述 MME 与代理呼叫会话控制功能 P-CSCF 之间的第二类型的第一信令消息, 将所述上行数据发送给所述应用服务器。
31、 根据权利要求 30所述的 MME, 其特征在于, 所述第三接收模块还 用于在接收所述第一类型的第一信令消息之前, 接收所述终端设备发送的附 着请求消息, 以及在所述第三发送模块向所述应用服务器发送第一 SIP注册 请求消息后, 通过所述 MME与所述 P-CSCF之间的第二类型的第三信令消 息, 接收所述应用服务器在接收到所述终端设备对应的 SIP标识后返回的第 ― SIP注册完成消息, 所述附着请求消息包括所述终端设备的标识; 所述 MME还包括:
获取模块, 用于根据所述终端设备的标识, 获取所述终端设备对应的会 话初始协议 SIP标识, 并生成所述第一 SIP注册请求消息, 所述第一 SIP注 册请求消息包括所述终端设备的标识和所述终端设备对应的 SIP标识;
所述第三发送模块还用于通过所述 MME与所述 P-CSCF之间的第二类 型的第二信令消息向所述应用服务器发送所述第一 SIP注册请求消息, 以及 在所述第三接收模块接收到所述第一 SIP注册完成消息后, 向所述终端设备 发送附着接受消息, 所述附着接受消息包括所述第一 SIP注册完成消息; 其中, 所述终端设备与所述 MME之间仅存在信令连接。
32、 根据权利要求 31所述的 MME, 其特征在于, 所述获取模块用于根 据所述终端设备的标识, 获取所述终端设备对应的 SIP标识包括:
所述获取模块具体用于向位置归属服务器 HSS发送位置更新请求消息, 所述位置更新请求消息包括所述终端设备的标识, 并接收所述 HSS根据所述 终端设备的标识返回的所述终端设备的标识和所述终端设备对应的 SIP标识 之间的映射关系; 或者
所述获取模块具体用于根据所述终端设备的标识, 生成所述终端设备对 应的 SIP标识。
33、 根据权利要求 30所述的 MME, 其特征在于, 所述第三接收模块还 用于在接收所述第一类型的第一信令消息之前, 接收所述终端设备发送的附 着请求消息,以及在所述第三发送模块向所述终端设备发送附着接受消息后, 类型的第二信令消息,并在所述第三发送模块向所述应用服务器发送第 ― SIP 注册请求消息后, 接收所述应用服务器在接收到所述终端设备对应的 SIP标 识后返回的第一 SIP注册完成消息; 所述附着请求消息包括所述终端设备的 标识, 所述第一类型的第二信令消息包括所述第一 SIP注册请求消息, 所述 第一 SIP注册请求消息包括所述终端设备的标识和所述终端设备对应的 SIP 标识;
所述 MME还包括: 分配模块, 用于为所述终端设备分配所述 IP地址; 所述第三发送模块还用于在所述第三接收模块接收到所述附着请求消息 后, 向所述终端设备发送所述附着接受消息, 所述附着接受消息包括所述 IP 地址, 以及在所述第三接收模块接收到所述第一类型的第二信令消息后, 通 过所述 MME与所述 P-CSCF之间的第二类型的第二信令消息, 将所述第一 SIP注册请求消息发送给所述应用服务器,以及在所述第三接收模块接收到所 述第一 SIP注册完成消息后, 向所述终端设备发送第一类型的第三信令消息, 所述第一类型的第三信令消息包括所述第一 SIP注册完成消息;
其中, 所述终端设备与所述 MME之间仅存在信令连接。
34、 根据权利要求 30所述的 MME, 其特征在于, 所述第三发送模块还 用于在所述第三接收模块接收所述第一类型的第一信令消息之前, 通过所述 MME与所述 P-CSCF之间的第二类型的第二信令消息, 向所述 P-CSCF发送 第二 SIP注册请求消息, 以使所述 P-CSCF将所述第二 SIP注册请求消息发 送给所述应用服务器, 所述第二类型的第二信令消息包括所述第二 SIP注册 请求消息, 所述第二 SIP注册请求消息包括所述 MME的标识和所述 MME 对应的 SIP标识;
所述第三接收模块还用于在所述第三发送模块发送所述第二 SIP注册请 求消息后, 通过所述 MME与所述 P-CSCF之间的第二类型的第三信令消息, 接收所述应用服务器在接收到所述 MME对应的 SIP标识后返回的第二 SIP 注册完成消息。
35、 根据权利要求 34所述的 MME, 其特征在于, 所述第三接收模块还 用于在接收到所述第二 SIP注册完成消息后, 接收所述终端设备发送的附着 请求消息, 所述附着请求消息包括所述终端设备的标识;
所述第三发送模块还用于在所述第三接收模块接收到所述附着请求消息 后, 向所述终端设备发送附着接受消息;
其中, 所述终端设备与所述 MME之间仅存在信令连接。
36、 根据权利要求 30-35任一项所述的 MME, 其特征在于, 所述第三接 收模块还用于通过所述 MME与所述 P-CSCF之间的第二类型的第四信令消 息, 接收所述应用服务器发送给所述终端设备的下行数据, 以及在所述第三 发送模块向所述终端设备发送寻呼消息后, 接收所述终端设备发送的服务请 求消息;
所述第三发送模块还用于在所述第三接收模块接收到所述下行数据后, 向所述终端设备发送所述寻呼消息, 以及在所述第三接收模块接收到所述服 务请求消息后, 向所述终端设备发送第一类型的第四信令消息, 所述第一类 型的第四信令消息包括所述下行数据。
37、 根据权利要求 30-35任一项所述的 MME, 其特征在于, 所述第三发 送模块用于通过所述 MME与代理呼叫会话控制功能 P-CSCF之间的第二类 型的第一信令消息, 将所述上行数据发送给所述应用服务器包括:
所述第三发送模块具体用于向 MSC 服务器发送第三类型的第一信令消 息, 所述第三类型的第一信令消息包括所述上行数据, 以使所述 MSC服务器 将所述上行数据封装在所述第二类型的第一信令消息中发送给所述 P-CSCF, 以将所述上行数据发送给所述应用服务器。
38、 根据权利要求 36所述的 MME, 其特征在于, 所述第三接收模块用 于通过所述 MME与所述 P-CSCF之间的第二类型的第四信令消息, 接收所 述应用服务器发送给所述终端设备的下行数据包括:
所述第三接收模块具体用于接收 MSC服务器发送的第三类型的第二信 令消息, 所述第三类型的第二信令消息是所述 MSC服务器根据所述 P-CSCF 发送的所述第二类型的第四信令消息生成的, 所述第三类型的第二信令消息 包括所述下行数据。
39、 一种移动性管理实体 MME, 其特征在于, 包括:
接收器, 用于接收基站发送的第一类型的第一信令消息, 所述第一类型 的第一信令消息是所述基站在接收到终端设备发送的无线资源控制 RRC 连 接完成消息后,根据所述终端设备发送的 RRC连接请求消息中的指示信息生 成的,所述 RRC连接完成消息包括所述终端设备发送给应用服务器的上行数 据, 所述第一类型的第一信令消息包括所述上行数据, 所述指示信息用于指 示所述基站仅为所述终端设备建立信令连接;
发送器, 用于通过所述 MME与代理呼叫会话控制功能 P-CSCF之间的 第二类型的第一信令消息 , 将所述上行数据发送给所述应用服务器。
40、 一种代理呼叫会话控制功能 P-CSCF, 其特征在于, 包括: 第四接收模块, 用于通过所述 P-CSCF与移动性管理实体 MME之间的 第二类型的第一信令消息, 接收终端设备发送给应用服务器的上行数据; 所 述第二类型的第一信令消息是所述 MME接收到基站发送的第一类型的第一 信令消息后, 根据所述第一类型的第一信令消息中的所述上行数据生成的, 所述第二类型的第一信令消息包括所述上行数据, 所述上行数据的数据量小 于预设数据量门限;
第四发送模块, 用于将所述上行数据发送给 S-CSCF, 以使所述 S-CSCF 将所述上行数据发送给所述应用服务器。
41、 根据权利要求 40所述的 P-CSCF, 其特征在于, 所述第四接收模块 还用于在接收所述上行数据之前, 通过所述 P-CSCF与所述 ΜΜΕ之间的第 二类型的第二信令消息, 接收所述 ΜΜΕ发送的第一 SIP注册请求消息, 并 在所述第四发送模块将所述第 ― SIP注册请求消息发送给所述应用服务器后 , 接收所述 S-CSCF发送的所述应用服务器在接收到所述终端设备对应的 SIP 标识返回的第一 SIP注册完成消息, 所述第一 SIP注册请求消息包括所述终 端设备的标识和所述终端设备对应的 SIP标识;
所述第四发送模块还用于在所述第四接收模块接收到所述第一 SIP注册 请求消息后, 将所述第一 SIP 注册请求消息发送给所述 S-CSCF, 以使所述 S-CSCF将所述第一 SIP注册请求消息发送给所述应用服务器,以及在所述第 四接收模块接收到所述第一 SIP注册完成消息后, 通过所述 P-CSCF与所述 MME之间的第二类型的第三信令消息,向所述 MME发送所述第一 SIP注册 完成消息。
42、 根据权利要求 40所述的 P-CSCF, 其特征在于, 所述第四接收模块 还用于在接收所述上行数据之前, 通过所述 P-CSCF与所述 MME之间的第 二类型的第二信令消息, 接收所述 MME发送的第二 SIP注册请求消息, 以 及在所述第四发送模块将所述第二 SIP注册请求消息发送给所述 S-CSCF后, 接收所述 S-CSCF发送的所述应用服务器在接收到所述 MME对应的 SIP标识 后返回的第二 SIP注册完成消息,所述第二 SIP注册请求消息包括所述 MME 的标识和所述 MME对应的 SIP标识;
所述第四发送模块还用于在所述第四接收模块接收到所述第二 SIP注册 请求消息后, 将所述第二 SIP 注册请求消息发送给所述 S-CSCF, 以使所述 S-CSCF将所述第二 SIP注册请求消息发送给所述应用服务器,以及在所述第 四接收模块接收到所述第二 SIP注册完成消息后, 通过所述 P-CSCF与所述 MME之间的第二类型的第三信令消息,向所述 MME发送所述第二 SIP注册 完成消息。
43、 根据权利要求 42所述的 P-CSCF, 其特征在于, 所述第四接收模块 还用于接收所述 S-CSCF发送的所述应用服务器发送给终端设备的下行数据 和所述 MME的地址信息,所述 MME的地址信息是所述 S-CSCF根据所述终 端设备对应的 SIP标识查询归属存储服务器 HSS获取的,所述 HSS存储有所 述终端设备的标识与所述终端设备对应的 SIP标识之间的映射关系, 以及所 述终端设备的标识与所述 MME的地址信息之间的映射关系;
所述第四发送模块还用于在所述第四接收模块接收到所述下行数据和所 述 MME的地址信息后,根据所述 MME的地址信息,通过所述 P-CSCF与所 述 MME之间的第二类型的第四信令消息, 向所述 MME发送所述下行数据。
44、 根据权利要求 40-42任一项所述的 P-CSCF, 其特征在于, 所述第四 接收模块用于通过所述 P-CSCF与移动性管理实体 MME之间的第二类型的 第一信令消息, 接收终端设备发送给应用服务器的上行数据包括:
所述第四接收模块具体用于接收 MSC服务器发送的所述第二类型的第 一信令消息, 所述第二类型的第一信令消息是所述 MSC 服务器根据所述 MME发送的第三类型的第一信令消息生成的,所述第三类型的第一信令消息 包括所述上行数据。
45、 根据权利要求 43所述的 P-CSCF, 其特征在于, 所述第四发送模块 用于根据所述 MME的地址信息,通过所述 P-CSCF与所述 MME之间的第二 类型的第四信令消息, 向所述 MME发送所述下行数据包括:
所述第四发送模块具体用于向 MSC 服务器发送的所述第二类型的第四 信令消息,以使所述 MSC服务器将所述第二类型的第四信令消息中的所述下 行数据封装在第三类型的第二信令消息中发送给所述 MME。
46、 一种代理呼叫会话控制功能 P-CSCF, 其特征在于, 包括:
接收器, 用于通过所述 P-CSCF与移动性管理实体 MME之间的第二类 型的第一信令消息, 接收终端设备发送给应用服务器的上行数据; 所述第二 类型的第一信令消息是所述 MME接收到基站发送的第一类型的第一信令消 息后, 根据所述第一类型的第一信令消息中的所述上行数据生成的, 所述第 二类型的第一信令消息包括所述上行数据, 所述上行数据的数据量小于预设 数据量门限; 发送器, 用于将所述上行数据发送给 S-CSCF, 以使所述 S-CSCF将所述 上行数据发送给所述应用服务器。
47、 一种数据传输系统, 其特征在于, 包括: 权利要求 22-26任一项所 述的终端设备、 权利要求 28所述的基站、 权利要求 30-38任一项所述的移动 性管理实体 MME 和权利要求 40-45 任一项所述的代理呼叫会话控制功能 P-CSCF; 所述 P-CSCF与所述 MME连接。
PCT/CN2012/082430 2012-09-29 2012-09-29 数据传输方法、设备及系统 WO2014047920A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
CN201280001720.9A CN103891321B (zh) 2012-09-29 2012-09-29 数据传输方法、设备及系统
EP12885203.5A EP2884780B1 (en) 2012-09-29 2012-09-29 Data transmission method, device and system
PCT/CN2012/082430 WO2014047920A1 (zh) 2012-09-29 2012-09-29 数据传输方法、设备及系统
US14/671,724 US9549424B2 (en) 2012-09-29 2015-03-27 Data transmission method, device, and system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2012/082430 WO2014047920A1 (zh) 2012-09-29 2012-09-29 数据传输方法、设备及系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US14/671,724 Continuation US9549424B2 (en) 2012-09-29 2015-03-27 Data transmission method, device, and system

Publications (1)

Publication Number Publication Date
WO2014047920A1 true WO2014047920A1 (zh) 2014-04-03

Family

ID=50386887

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/082430 WO2014047920A1 (zh) 2012-09-29 2012-09-29 数据传输方法、设备及系统

Country Status (4)

Country Link
US (1) US9549424B2 (zh)
EP (1) EP2884780B1 (zh)
CN (1) CN103891321B (zh)
WO (1) WO2014047920A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018006933A1 (en) 2016-07-04 2018-01-11 Huawei Technologies Co., Ltd. Session management for massive machine type communication in 5g networks
CN109246815A (zh) * 2017-05-22 2019-01-18 展讯通信(上海)有限公司 通信方法、寻呼方法及装置、存储介质、终端、基站
CN109247080A (zh) * 2016-06-03 2019-01-18 华为技术有限公司 传输信息的方法、用户设备、接入网设备和核心网设备

Families Citing this family (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103313225A (zh) * 2012-03-12 2013-09-18 中兴通讯股份有限公司 触发漫游mtc设备的系统、装置以及方法
US9526022B2 (en) 2012-08-03 2016-12-20 Intel Corporation Establishing operating system and application-based routing policies in multi-mode user equipment
US9036603B2 (en) 2012-08-03 2015-05-19 Intel Corporation Network assistance for device-to-device discovery
US9554296B2 (en) * 2012-08-03 2017-01-24 Intel Corporation Device trigger recall/replace feature for 3GPP/M2M systems
US8913518B2 (en) 2012-08-03 2014-12-16 Intel Corporation Enhanced node B, user equipment and methods for discontinuous reception in inter-ENB carrier aggregation
US9191828B2 (en) 2012-08-03 2015-11-17 Intel Corporation High efficiency distributed device-to-device (D2D) channel access
US10477366B2 (en) * 2014-07-08 2019-11-12 Nokia Solutions And Networks Oy Apparatuses and methods to introduce flexible support for services
FR3043522A1 (fr) 2015-11-10 2017-05-12 Orange Transmission de donnees de volume variable dans un reseau mobile de communication
US10412674B2 (en) * 2016-01-27 2019-09-10 Samsung Electronics Co., Ltd. Method and apparatus for reducing signaling overhead and reducing battery of terminal
CN106792608B (zh) * 2016-09-29 2018-11-16 展讯通信(上海)有限公司 小数据包传输方法、装置及终端
US11283773B2 (en) * 2016-11-16 2022-03-22 Telefonaktiebolaget Lm Ericsson (Publ) Protecting user's anonymity when visiting foreign networks
US10075827B1 (en) 2017-03-07 2018-09-11 At&T Intellectual Proprety I, L.P. System and method for machine to machine subscriber information and retrieval protection
US11641381B2 (en) 2017-03-09 2023-05-02 T-Mobile Usa, Inc. Call setup timer triggered by network response
CN108495278B (zh) * 2018-02-11 2021-04-13 北京盛安同力科技开发有限公司 一种卫星网络中低时延资源控制的业务传输方法
US11343686B2 (en) * 2020-03-11 2022-05-24 Verizon Patent And Licensing Inc. Systems and methods for call session control function failover using dynamic routing techniques
CN115134767B (zh) * 2021-03-11 2024-02-09 上海大唐移动通信设备有限公司 提升信令软采集设备性能的方法、装置及存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101931898A (zh) * 2009-06-26 2010-12-29 华为技术有限公司 用户面数据的传输方法、装置及系统
CN102413445A (zh) * 2010-09-26 2012-04-11 电信科学技术研究院 一种数据的传输方法和设备
CN102457825A (zh) * 2010-10-15 2012-05-16 电信科学技术研究院 一种数据的传输方法和设备

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101213285B1 (ko) * 2006-01-04 2012-12-17 삼성전자주식회사 이동통신 시스템에서 아이들모드 단말기의 세션 설정 프로토콜 데이터를 전송하는 방법 및 장치
CN100407876C (zh) * 2006-01-26 2008-07-30 华为技术有限公司 一种用户设备附着方法
US20100255810A1 (en) * 2007-10-24 2010-10-07 Naoto Itaba Mobile communication system, communication method, and mobile station, radio base station, and higher-order apparatus for radio base station used for mobile communication system and communication method
JPWO2010143428A1 (ja) * 2009-06-12 2012-11-22 パナソニック株式会社 基地局制御装置および携帯端末
CN102149139B (zh) * 2010-02-10 2016-02-24 中兴通讯股份有限公司 一种mtc系统的上行数据发送方法和系统
US8811281B2 (en) * 2011-04-01 2014-08-19 Cisco Technology, Inc. Soft retention for call admission control in communication networks
US8965415B2 (en) * 2011-07-15 2015-02-24 Qualcomm Incorporated Short packet data service
US20130053029A1 (en) * 2011-08-23 2013-02-28 Kirankumar Anchan Supporting services to a roaming user equipment within a local network of a wireless communications system
US8929290B2 (en) * 2011-08-26 2015-01-06 Qualcomm Incorporated In-band signaling to indicate end of data stream and update user context
CN102340754B (zh) * 2011-09-23 2014-07-23 电信科学技术研究院 数据发送和接收方法及设备
US8918453B2 (en) * 2012-01-03 2014-12-23 Qualcomm Incorporated Managing data representation for user equipments in a communication session
US9055520B2 (en) * 2012-12-19 2015-06-09 Cisco Technology, Inc. Systems, methods and media for mobile management entity (MME) selection by Evolved Node B (eNodeB)

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101931898A (zh) * 2009-06-26 2010-12-29 华为技术有限公司 用户面数据的传输方法、装置及系统
CN102413445A (zh) * 2010-09-26 2012-04-11 电信科学技术研究院 一种数据的传输方法和设备
CN102457825A (zh) * 2010-10-15 2012-05-16 电信科学技术研究院 一种数据的传输方法和设备

Non-Patent Citations (1)

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

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109247080A (zh) * 2016-06-03 2019-01-18 华为技术有限公司 传输信息的方法、用户设备、接入网设备和核心网设备
US10904866B2 (en) 2016-06-03 2021-01-26 Huawei Technologies Co., Ltd. Information transmission method, user equipment, access network device, and core network device
CN109247080B (zh) * 2016-06-03 2021-05-18 华为技术有限公司 传输信息的方法、用户设备、接入网设备和核心网设备
WO2018006933A1 (en) 2016-07-04 2018-01-11 Huawei Technologies Co., Ltd. Session management for massive machine type communication in 5g networks
CN109246815A (zh) * 2017-05-22 2019-01-18 展讯通信(上海)有限公司 通信方法、寻呼方法及装置、存储介质、终端、基站

Also Published As

Publication number Publication date
EP2884780A4 (en) 2015-08-12
CN103891321B (zh) 2017-11-24
EP2884780A1 (en) 2015-06-17
CN103891321A (zh) 2014-06-25
US9549424B2 (en) 2017-01-17
US20150208450A1 (en) 2015-07-23
EP2884780B1 (en) 2019-02-20

Similar Documents

Publication Publication Date Title
WO2014047920A1 (zh) 数据传输方法、设备及系统
CN114189815B (zh) 移动通信系统中终端通信的方法和装置
US9125003B2 (en) Machine to machine service management device, network device, and method processing service system
JP5803696B2 (ja) ネットワークシステム,オフロード装置及びオフロード装置の利用者識別情報取得方法
CN112584371B (zh) 漫游信令消息发送的方法、相关设备和通信系统
US9473877B2 (en) Uplink/downlink transmission method for small amount of data, and corresponding terminal and mobility management unit
CN111630824B (zh) 用于卸载数据流量的方法和计算机可读介质
EP2382816A1 (en) Method and arrangement for load balancing in a wireless communication system
WO2010121511A1 (zh) 多网接入控制方法、通讯系统以及相关设备
KR20090016430A (ko) 패킷 스위칭 도메인에서 단말의 위치 등록 방법 및 장치
EP2482567B1 (en) Method and apparatus for status transition
WO2011095100A1 (zh) 一种对本地ip连接的建立进行控制的方法和系统
WO2012094957A1 (zh) 一种对mtc终端进行移动性管理的方法和系统
WO2012041219A1 (zh) 启动阶段指示发送及网关节点选择方法、系统和设备
KR20180012325A (ko) Nfv를 이용하는 mtc 서비스 관리
WO2014180114A1 (zh) 实现mtc监控的方法及装置
WO2010133107A1 (zh) 家用基站网关转发消息至家用基站的方法及系统
CN107438290B (zh) 一种小数据传输的连接建立方法、scef实体、mme
WO2012130133A1 (zh) 一种接入点及终端接入方法
JP6191768B2 (ja) 移動無線通信装置からのデータ転送
WO2011017979A1 (zh) 支持ip分流的通信系统中资源管理方法与装置
WO2012028071A1 (zh) 一种查询本地网关的方法和系统
WO2013152545A1 (zh) 一种连接建立的方法及网关单元
WO2011038609A1 (zh) 本地连接信息的发送方法及装置
WO2011110022A1 (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: 12885203

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2012885203

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE