WO2014032469A1 - 一种通信连接释放方法、装置及系统 - Google Patents

一种通信连接释放方法、装置及系统 Download PDF

Info

Publication number
WO2014032469A1
WO2014032469A1 PCT/CN2013/078345 CN2013078345W WO2014032469A1 WO 2014032469 A1 WO2014032469 A1 WO 2014032469A1 CN 2013078345 W CN2013078345 W CN 2013078345W WO 2014032469 A1 WO2014032469 A1 WO 2014032469A1
Authority
WO
WIPO (PCT)
Prior art keywords
group
release
devices
core network
bearer
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2013/078345
Other languages
English (en)
French (fr)
Inventor
张英
陈东
全海洋
艾明
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
China Academy of Telecommunications Technology CATT
Original Assignee
China Academy of Telecommunications Technology CATT
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 China Academy of Telecommunications Technology CATT filed Critical China Academy of Telecommunications Technology CATT
Publication of WO2014032469A1 publication Critical patent/WO2014032469A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H04W4/08—User group management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release

Definitions

  • the present invention relates to communication technologies, and in particular, to a communication connection release method, apparatus, and system. Background technique
  • M2M (Machine to Machine) communication is a trend of intelligent development in the future.
  • the MTC (Machine Type Communications) function needs to be supported in the third generation mobile communication system and its long term evolution system.
  • Smart Metering has received extensive attention as a typical MTC application scenario.
  • the Smart Metering service has the characteristics of high distribution density, low network-to-device control requirements, long time period of service on the device, business time, centralized application, single application and fixed location, and centralized reporting of related services. Data is the primary means of communication.
  • MTC enables the integration of many different types of communication technologies, such as machine-to-machine communication, machine control communication, human-computer interaction communication, and mobile internet communication, to promote social production and lifestyle development.
  • MTC communication is also known as Machine-to-machine (inter-machine) communication or the Internet of Things.
  • Network capacity is designed for communication between people. If it is desired to utilize the mobile communication network to support MTC communication, it is necessary to optimize the mechanism of the mobile communication system according to the characteristics of the MTC communication, so that it can be better in the case where the traditional human-to-human communication is not affected or less affected. Implement MTC communication.
  • MTC devices have low mobility; MTC devices and network side data transmission time is controllable; MTC network and network side data transmission for data transmission real-time The requirements are not high, that is: time-tolerant; MTC equipment is limited in energy and requires extremely low power consumption; only small data is transmitted between the MTC device and the network side; MTC devices can be managed in groups.
  • an MTC device can have one or more of the features described above.
  • the UMTS (Universal Mobile Telecommunication System) system network architecture is shown in Figure 1.
  • the UMTS system consists of the core network, RNC (Radio Network Controller), B (NodeB, base station) and A UE (User Equipment, Device, Device) is configured, wherein the UE and the NB communicate through an air interface (Uu interface), and the B and the RNC form a RAN (Radio Access Network), and the Lub passes through the Lub. Interface communication, between the RAN and the core network through the Iu interface Line communication.
  • the communication connection is established through a series of interaction processes, including air interface link establishment (RRC connection), lub interface radio link establishment, and lu interface communication connection establishment, where RRC (Radio Resource Connection, radio resource connection) connection and lu interface connection are established for each UE, mainly used to maintain the context of the device at different nodes of the network.
  • RRC Radio Resource Connection, radio resource connection
  • lu interface communication connection establishment where RRC (Radio Resource Connection, radio resource connection) connection and lu interface connection are established for each UE, mainly used to maintain the context of the device at different nodes of the network.
  • the communication connection release process defined in the current 3GPP (3rd Generation Partnership Project) standard is shown in Figure 2, where the release process can be triggered by the RAN or by the core network. If triggered by the core network, the first message Iu release request in Figure 2 does not need to appear.
  • the specific process is as follows:
  • Step S201 For the scenario triggered by the RAN, when the RAN detects that the RRC connection for the device has been released, or detects that the radio resource needs to be released, the SGSN (Serving GPRS Support Node, Serving GPRS Support Node; GPRS, General Packet Radio Service, The general packet radio service sends a lu Release Request message.
  • the SGSN Server GPRS Support Node, Serving GPRS Support Node
  • GPRS General Packet Radio Service
  • Step S202 The SGSN performs a lu interface connection release by sending a lu Release Command message to the RAN.
  • Step S203 The RNC initiates an RRC connection release message to the device (MS) to trigger an RRC connection release process.
  • Step S205 The RNC initiates a radio link release message (Radio Link Deletion) message to the NodeB to trigger a lub bearer and a context release process.
  • a radio link release message Radio Link Deletion
  • Step S206 The NodeB returns a radio link release response message (Radio Link Deletion Response) message to the RNC.
  • Step S207 The RAN confirms by sending a lu Release Completion message to the SGSN.
  • connection release to the device can be completed.
  • the device In the LTE (Long Term Evolution) system, the device is also released. Specifically, the LTE system network architecture is shown in Figure 3.
  • the LTE system consists of the core network, e B (base station), and UE.
  • the communication is performed between the eNB and the core network through the air interface (Uu interface), and the eNB communicates with the core network through the S1 interface.
  • Uu interface air interface
  • the LTE system is similar to the UMTS system, and the specific communication connection release process is as shown in FIG.
  • MTC communication involves a group of equipment, such as water meters, electricity meters, gas meters and other industrial applications.
  • Water, electricity, and gas meter equipment in a certain area can belong to an MTC user/MTC server (water, electricity, The management platform of the gas company), whether from the perspective of the MTC user or from the perspective of the operator, it is beneficial to manage based on a group as a whole.
  • the MTC user when the MTC user needs to send public information to the owned MTC device or needs to page the dedicated signaling to send the same information content, it will cause a certain amount of waste of resources, and if it can trigger or send the same data based on the group, It will greatly reduce signaling overhead and improve resource utilization. From the perspective of the operator, group-based charging and the like can be performed for a group of devices, which is convenient for management.
  • the release of the communication connection is for one device.
  • the intra-group device completes the data transmission, if each device is used to release the connection, the resulting Sl/ The Iu interface signaling and air interface signaling load is large, and the efficiency of releasing the communication connection is also low.
  • Embodiments of the present invention provide a communication connection release method, apparatus, and system, to reduce interface signaling and air interface signaling load, and improve communication link release efficiency.
  • a communication connection release method includes:
  • the termination data receiving indication is used to instruct the core network to initiate a group connection release process, and release a communication connection of the devices in the group.
  • a communication connection release method includes:
  • the core network receiving monitoring device receives the termination data receiving indication of the carried group identifier when each device in the group reaches the communication connection release condition;
  • the core network initiates a group connection release process, releasing the communication connection of the devices in the group.
  • a communication connection release device includes:
  • a determining unit configured to determine that each device in the group reaches a communication connection release condition
  • a sending unit configured to send, to the core network, a termination data receiving indication that carries the group identifier, where the termination data receiving indication is used to instruct the core network to initiate a group connection release process, and release a communication connection of the devices in the group.
  • a communication connection release device includes:
  • the indication receiving unit is configured to receive, by the monitoring device, a termination data receiving indication of the carried group identifier that is sent when each device in the group reaches the communication connection release condition;
  • connection release unit is configured to initiate a group connection release process, and release a communication connection of the devices in the group.
  • a communication connection release system includes:
  • a monitoring device configured to determine that each device in the group reaches a communication connection release condition; and send, to the core network, a termination data receiving indication that carries a group identifier, where the termination data receiving indication is used to indicate that the core network initiates a group connection release process, Release the communication connection of the devices in the group;
  • the core network is configured to receive, by the monitoring device, a termination data receiving indication of the carried group identifier when each device in the group reaches the communication connection release condition; initiate a group connection release process, and release the communication connection of the devices in the group.
  • the embodiment of the invention provides a communication connection release method, device and system.
  • the device is uniformly released, thereby avoiding separate release of each device, thereby reducing Interface signaling and air interface signaling load improve the efficiency of communication connection release.
  • FIG. 1 is a schematic diagram of a network structure of a UMTS system in the background art
  • FIG. 3 is a schematic diagram of a network structure of an LTE system in the background art
  • FIG. 5 is a flowchart of a method for releasing a communication connection according to an embodiment of the present invention
  • FIG. 6 is a flowchart of a communication connection release method corresponding to Embodiment 1 according to an embodiment of the present invention
  • FIG. 7 is a flowchart of a communication connection release method corresponding to Embodiment 2 according to an embodiment of the present invention.
  • FIG. 8 is a flowchart of a communication connection release method corresponding to Embodiment 3 according to an embodiment of the present invention.
  • FIG. 9 is a flowchart of a communication connection release method corresponding to Embodiment 4 according to an embodiment of the present invention.
  • FIG. 10 is a second flowchart of a method for releasing a communication connection according to an embodiment of the present invention.
  • FIG. 11 is a schematic structural diagram of a communication connection release device according to an embodiment of the present invention.
  • FIG. 12 is a second schematic structural diagram of a communication connection release device according to an embodiment of the present invention.
  • FIG. 13 is a schematic structural diagram of a communication connection release system according to an embodiment of the present invention.
  • FIG. 14 is a schematic structural diagram of a monitoring device according to an embodiment of the present invention.
  • FIG. 15 is a second schematic structural diagram of a core network device according to an embodiment of the present invention. detailed description
  • the embodiment of the invention provides a communication connection release method, device and system.
  • the communication connection release method includes:
  • Step S501 Determine that each device in the group reaches a communication connection release condition
  • Step S502 Send a termination data receiving indication carrying the group identifier to the core network, where the termination data receiving indication is used to indicate the core network to initiate the group connection release process, and release the communication connection of the devices in the group.
  • the device determines that each device in the group meets the communication connection release condition, and specifically includes: determining that each device in the group completes data interaction; or determining that the preset timer expires.
  • the communication connection release method may be performed by an MTC server (MTC server) or an MTC user (MTC device), or may be performed by an eNodeB (e B, an evolved base station) in the LTE network, or may be an RNC or a NodeB in the UMTS network ( Base station) execution.
  • MTC server MTC server
  • MTC user MTC device
  • eNodeB e B, an evolved base station
  • RNC Radio Network Controller
  • the core network receives the termination data reception indication, and the core network initiates an Iu/S1 carrying the group identifier (Group ID) to the RNC (UMTS) / eNB (LTE) through the Iu (UMTS) / SI (LTE) interface.
  • the group connection indication triggers the connection release process.
  • the RNC (UMTS) / eNB (LTE) releases the Iu/Sl related contexts of all the devices in the group, and notifies the devices in the group to perform RRC connection release by means of group broadcast.
  • the Iu/S group 1 connection release is completed to the core network; the device performs the release process of the radio resource after reading the RRC connection release indication, and does not need to feed back to the network.
  • each device needs to establish an independent Iu/Sl bearer and context, so the release process of a set of Iu/Sl connections is triggered by an Iu/S1 connection indication.
  • the RNC (UMTS) / eNB (LTE) is required to predetermine the Iu/S1 bearer and the correspondence between the context and the group.
  • One possible solution is to notify the RNC (UMTS) when the Iu/S1 connection is established for each device.
  • /eNB (LTE) The group identification information to which the connection belongs, when the RNC (UMTS) / eNB (LTE) receives the Iu/S1 group connection release indication carrying the group ID (Group ID), all groups can be released.
  • the Iu/Sl related bearer and context of the device is required to predetermine the Iu/S1 bearer and the correspondence between the context and the group.
  • the release process of the lub interface bearer is also involved.
  • the lub bearer group release mode can also be used. That is, a lub group connection indication triggers a release process of a set of lub connections.
  • the NodeB needs to predetermine the lub bearer and the context and group correspondence.
  • One possible solution is to establish a lub connection for each device.
  • the BAP the wireless connection establishment process notifies the NodeB of the group identification information to which the connection belongs
  • the NodeB receives the lub group connection release indication carrying the group ID (Group ID)
  • the NodeB can release all the devices in the group. Lub related bearers and context.
  • the MTC server or the MTC user triggers the group connection release.
  • the core network initiates a group connection release process, and releases the communication connection of the devices in the group, including: The core network releases the internal bearer of the core network of all devices in the group according to the group identifier (ie, the S11 interface (MME and Serving).
  • group identifier ie, the S11 interface (MME and Serving).
  • the interface between the GWs is carried by the device, and sends a release indication message carrying the group identifier to the base station;
  • the base station After receiving the release indication message, the base station releases the S1 interface bearer and the context of the devices in the group, and notifies the device in the group to perform the RRC connection release.
  • the base station feeds back the release completion message to the core network.
  • the RRC connection release indication may be sent to the intra-group device in the group broadcast mode, and the device in the group is notified to perform the RRC connection release. After the RRC connection release indication is performed, the radio resource release process is performed. After the release is completed, no feedback is required, thereby further reducing the network load.
  • the core network can determine the bearer of the device in the group according to the group identifier, and the core network can determine the correspondence between the group identifier and the bearer when the bearer is established, so that when the bearer needs to be released, the core network can be the core network according to the group.
  • the base station determines the correspondence between the group identifier and the bearer, so that when the bearer needs to be released, the base station may also use the group identifier and the group identifier and bearer and context determined when the bearer and the context are established. Correspondence, release the S1 interface bearer and context of all devices in the group.
  • the release process of triggering the connection release by the MTC server or the MTC user includes:
  • Step S601 The MTC server or the MTC user determines that each device in the group reaches the communication connection release condition, and sends an termination data reception indication to the MTC IWF (Interworking Functionality) entity in the core network, where the indication includes the identifier group.
  • Group ID group ID
  • the specific detection means may be: determining that the device data release in the group has been received, or some device data is not received but has exceeded the preset. Waiting timer.
  • Step S602 The MTC IWF sends an end data transmission indication to the MME (Mobility Management Element), where the information includes a group identifier, etc.; the termination data transmission indication may be sent by using a newly defined message, or may be in an existing message. Add relevant information to achieve the termination of the transmission of the data transmission indication;
  • MME Mobility Management Element
  • the termination data transmission indication may be sent by using a newly defined message, or may be in an existing message. Add relevant information to achieve the termination of the transmission of the data transmission indication;
  • Step S603 The MME sends a Release Group Access Bearer Request to the Serving GW, where the request carries the group identifier.
  • Step S604 The Serving GW releases the user plane bearer of the S11 interface related to the device in the group according to the group ID carried in the bearer request of the release group connection. Specifically, the Serving GW can access the device in the group when the Serving GW establishes the bearer in the group. The group ID and other information identifies the group to which the bearer belongs. When the Serving GW receives the release group connection bearer request that carries the group identifier, the Serving GW can release the bearer identified as belonging to the group.
  • Step S605 The Serving GW returns a Release Group Access Bearer Response message to the MME.
  • Step S606 The MME sends an S1AP message, a SI group Context Release Command, to the eNB, where the message carries the Group ID, and initiates the S1 bearer and the context release process of the device in the group.
  • RAN Radio Access Network
  • RAN shared RAN shared
  • PLMNs Public Land Mobile Network
  • Step S607 After receiving the SI group Context Release Command message carrying the group ID, the eNB releases the S1 bearer and the context of all the devices in the group identified by the group ID. Specifically, the eNB can establish the intra-group device S1 bearer and In the context of the context, the group, such as the Group ID, carried in the INITIAL CONTEXT SETUP REQUEST message identifies the group to which the established bearer belongs, so that when the SI group Context Release Command message carrying the Group ID is received, the eNB The bearer and the context belonging to the group are released; wherein the SI group Context Release Command message may be a newly defined S1AP message, or may modify the existing SI Context Release Command message. Group ID and other related information.
  • the SI group Context Release Command message may be a newly defined S1AP message, or may modify the existing SI Context Release Command message. Group ID and other related information.
  • Step S608 The eNB sends an RRC connection release indication to the intra-group device, and after receiving the RRC connection release indication, the intra-group device determines, according to the group ID and other information carried in the RRC connection release indication, that the message belongs to the group, The connection is released, and the stored context and resource configuration information is deleted.
  • the RRC connection release indication may notify the devices in the group by means of group broadcast.
  • the "group broadcast" mode may be through the G-RNTK Group Radio Network Temporary Identity, the group wireless network temporary.
  • the PDCCH (Physical Downlink Control Channel) scheduling group in the Scheduling Group reads the PDSCH (Physical Downlink Shared Channel).
  • the RRC connection release indication carried in the information of the shared channel), wherein the RRC connection Release indication includes the Group ID.
  • the RRC connection release indication may carry the PLMN ID to indicate the PLMN to which the Group ID belongs.
  • the RRC connection release indication is sent to the intra-group device, the RRC-related context information of the stored intra-group device and the related configuration information are deleted, and the S1AP message SI Context Release Complete is completed.
  • the MME notifies the completion of the connection release in the group.
  • the message may be a newly defined S1AP message, or may be added with information such as a Group ID in the current SI RELEASE COMPLETE message.
  • the eNB triggers a group connection release.
  • the core network initiates a group connection release process, and releases the communication connection of the devices in the group, including:
  • the core network releases the internal bearer of the core network of all the devices in the group according to the group identifier (ie, the S11 interface (the interface between the MME and the Serving GW)
  • the device bears, and sends a release indication message carrying the group identifier to the base station;
  • the base station After receiving the release indication message, the base station releases the S1 interface bearer and the context of the devices in the group, and notifies the device in the group to perform the RRC connection release.
  • the base station feeds back the release completion message to the core network.
  • the RRC connection release indication may be sent to the intra-group device by the group broadcast mode, and the device in the group is notified to perform the RRC connection release; After the RRC connection release indication is performed, the radio resource release process is performed, and after the release is completed, no feedback is required, thereby further reducing the network load.
  • the core network can determine the bearer of the device in the group according to the group identifier, and the core network can determine the correspondence between the group identifier and the bearer when the bearer is established, so that when the bearer needs to be released, the core network can be the core network according to the group.
  • the base station determines the correspondence between the group identifier and the bearer, so that when the bearer needs to be released, the base station may also use the group identifier and the group identifier and bearer and context determined when the bearer and the context are established. Correspondence, release the S1 interface bearer and context of all devices in the group.
  • the release process of triggering the group connection release by the eNB includes: Step S701: The eNB determines that each device in the group reaches the communication connection release condition, and sends the termination data to the MME in the core network. Receiving an indication, where the indication includes information such as a group ID of the identification group;
  • the eNB performs the detection of the device data reporting in the group.
  • the specific detection means may be: comparing the number of reported devices in the group with the number of devices in the group obtained in advance from the MME, where the eNB needs to determine the belonging group.
  • the data of the internal device is required to carry the group ID that is visible to the eNB when the data is reported by the device in the group, and may be combined with a preset waiting timer or the like; or the eNB performs the activity detection of the device in the group. If the device data is reported in the group, the device data reporting in the group can be judged to be completed.
  • SI group Context Release Request After detecting that the device data in the group is received, e B requests the MME to release the bearer and context associated with the group through the S1AP message: SI group Context Release Request, and the message needs to include the Group ID information.
  • the Iu group Context Release Request may be a newly defined SI AP message, or may be a group ID information added to the SI Context Release Request message.
  • Step S702 - Step S708 is the same as step S603 - step S609 in the first embodiment, and the description will not be repeated here.
  • the MTC server or the MTC user triggers the group connection release.
  • the core network initiates a group connection release process, and releases the communication connection of the devices in the group, including:
  • the core network releases the internal bearer of the core network of all the devices in the group according to the group identifier (that is, the Gp interface (the interface between the SGSN and the GGSN) The device bears), and sends a release indication message carrying the group identifier to the radio network controller RNC;
  • the RNC After receiving the release indication message, the RNC releases the Iu interface bearer and context of all devices in the group, and notifies the device in the group to perform RRC connection release.
  • the RNC feeds back the release completion message to the core network.
  • the RNC releases the Iu interface bearer and context of all devices in the group, and includes:
  • the RNC informs the base station to release the Iub interface bearer and context of all devices in the group.
  • the RRC connection release indication may be sent to the intra-group device in the group broadcast mode, and the device in the group is notified to perform the RRC connection release. After the RRC connection release indication is performed, the radio resource release process is performed. After the release is completed, no feedback is required, thereby further reducing the network load.
  • the core network can determine the bearer of the device in the group according to the group identifier, and the core network can determine the correspondence between the group identifier and the bearer when the bearer is established, so that when the bearer needs to be released, the core network can be the core network according to the group.
  • the RNC determines the correspondence between the group identifier and the bearer, so that when the bearer needs to be released, the RNC can also determine the group identifier and bearer and context determined according to the group identifier and the bearer and context. Correspondence, release the Iu interface bearer and context of all devices in the group.
  • the release process of triggering the connection release by the MTC server or the MTC user includes:
  • Step S801 the MTC server or the MTC user determines that each device in the group reaches the communication connection release condition. Sending an end data receiving indication to the MTC IWF entity in the core network, where the indication includes information such as a group ID (group identifier) of the identifier group;
  • the specific detection means may be: determining that the device data release in the group has been received, or some device data is not received but has exceeded the preset. Waiting timer.
  • Step S802 The MTC IWF sends an end data transmission indication to the SGSN, where the group identifier and the like information is included; the termination data transmission indication may be sent by using a newly defined message, or the related information may be added to the existing message to terminate the data transmission. Sending of instructions;
  • Step S803 The SGSN sends a Release Group Access Bearer Request to the GGSN (Gateway GPRS Support Node), where the request carries the group identifier.
  • Step S804 The GGSN carries the bearer according to the release group connection bearer request.
  • the group ID is used to release the user plane bearer of the Gp interface in the core network related to the device in the group. Specifically, when the GGSN establishes the device bearer in the group, the group to which the bearer belongs is identified by the group identifier and other information, when the GGSN receives When the release group that carries the group ID is connected to the bearer request, the GGSN can release the bearer identified as belonging to the group.
  • Step S805 The GGSN returns a Release Group Access Bearer Response message to the SGSN.
  • Step S806 The SGSN sends a RANAP message Iu group Context Release Command to the RNC, where the message carries the Group ID, and initiates the Iu bearer and the context release process of the device in the group.
  • the RAN side cannot be grouped according to the Group ID zone because the same Group ID may be generated in different PLMNs.
  • the Iu group Context Release Command message needs to be carried.
  • the PLMN ID indicates the PLMN to which the Group ID belongs;
  • Step S807 After receiving the Iu group Context Release Command message carrying the Group ID, the RNC releases the Iu bearer and the context of all the devices in the group identified by the Group ID. Specifically, the RCU can establish the Iu bearer in the group.
  • RAB ASSIGNMENT REQUEST Radio Access Bearer Assignment Request, RAB, Radio Access Bearer, Radio Access Bearer
  • the Iu group Context Release Command message of the Group ID the RNC releases the bearer and the context belonging to the group; wherein, the Iu group Context Release Command message may be a newly defined S1AP message, or may be an existing RAB ASSIGNMENT REQUEST The message is modified to add related information such as group ID.
  • Step S808 The RNC sends an RRC connection release indication to the intra-group device.
  • the device in the group determines, according to the group ID and other information carried in the RRC connection release indication, that the group belongs to the group. The information is released, and the RRC connection is released, and the stored context and resource configuration information are deleted.
  • the RRC connection release indication may notify the devices in the group by means of group broadcast.
  • the "group broadcast" mode may be through G-RNTI (all preset group characteristics) The device needs to monitor the identifier.
  • the scrambled HS-SCCH (High Speed Shared Control Channel) scheduling group device reads the HS-PDSCH (High Speed Physical Downlink Shared Channel) information.
  • the RRC connection release indication is carried in the RRC connection release indication, and the RRC connection release indication includes the group ID. After the group ID in the device interpretation message is the group to which the device belongs, the RRC connection is released, and the network is not required to be released after the connection is released. Give feedback. It should be noted that, in the RAN sharing scenario, the RRC connection release indication may carry the PLMN ID to indicate the PLMN to which the Group ID belongs.
  • Step S809 After the RNC sends the RRC connection release indication to the intra-group device, the RRC deletes the RRC related context information of the stored intra-group device and related configuration information, and sends an Iub group Context Release Command to the NodeB.
  • the Iub Group Context Release Command message may be a newly defined B AP (NodeB Application Part) message, or may modify an existing RADIO LINK SETUP REQUEST message.
  • B AP NodeB Application Part
  • Step S810 The NodeB releases the Iub bearer and the context of all the devices in the group. Similarly, when the NodeB establishes the intra-group device Iub bearer and the context, the NodeB can carry the RADIO LINK SETUP REQUEST message (the RNC sends the NodeB) in the BAP process.
  • the information such as the group ID identifies the group to which the established bearer belongs, so that when the Iub group connection release message carrying the group ID is received, the RNC releases the bearer and the context belonging to the group.
  • Step S811 The NodeB returns an Iub Group Context Release Response message to the RNC.
  • Step S812 The RNC notifies the MME that the intra-group connection release is completed by the RANAP message IuContext Release Complete. It should be noted that the message may be a newly defined RANAP message, or may be added with a message such as a Group ID in the current Iu RELEASE COMPLETE message.
  • This embodiment is in the UMTS network, triggered by the RNC or NodeB trigger group connection.
  • the core network initiates a group connection release process, and releases the communication connection of the devices in the group, including:
  • the core network releases the internal bearer of the core network of all the devices in the group according to the group identifier (that is, the Gp interface (the interface between the SGSN and the GGSN) The device bears), and sends a release indication message carrying the group identifier to the radio network controller RNC;
  • the RNC releases the Iu interface bearer and context of all devices in the group, and notifies the device in the group to perform RRC connection release.
  • the RNC feeds back the release completion message to the core network.
  • the RNC releases the Iu interface bearer and context of all devices in the group, and includes:
  • the RNC informs the base station to release the Iub interface bearer and context of all devices in the group.
  • the RRC connection release indication may be sent to the intra-group device in the group broadcast mode, and the device in the group is notified to perform the RRC connection release. After the RRC connection release indication is performed, the radio resource release process is performed. After the release is completed, no feedback is required, thereby further reducing the network load.
  • the core network can determine the bearer of the device in the group according to the group identifier, and the core network can determine the correspondence between the group identifier and the bearer when the bearer is established, so that when the bearer needs to be released, the core network can be the core network according to the group.
  • the RNC determines the correspondence between the group identifier and the bearer, so that when the bearer needs to be released, the RNC can also determine the group identifier and bearer and context determined according to the group identifier and the bearer and context. Correspondence, release the Iu interface bearer and context of all devices in the group.
  • the release process of the RNC triggering the group connection release includes: Step S901: The RNC determines that each device in the group reaches the communication connection release condition, and sends the termination data to the SGSN in the core network. Receiving an indication, where the indication includes information such as a group ID of the identification group;
  • the RNC performs the detection of the device data reporting in the group.
  • the specific detection means may be: comparing the number of devices reported in the group with the number of devices in the group obtained in advance from the SGSN, where the RNC needs to determine the belonging group.
  • the data of the internal device is required to carry the Group ID of the RNC when the data is reported by the device in the group.
  • the group ID can be combined with the preset waiting timer.
  • the RNC can check the activity of the device in the group. If the device data is reported, you can judge that the device data reporting in the group is complete.
  • the RNC After detecting that the device data in the group is received, the RNC requests the SGSN to release the bearer and context associated with the group through the RANAP message: Iu group Context Release Request, and the message needs to include the Group ID information.
  • the Iu group Context Release Request may be a newly defined RANAP message, or may be a group ID information added to the Iu Release Request message.
  • this step can also be performed by the NodeB.
  • Steps S902 to S911 are the same as steps S803 to S812 in the third embodiment, and the description will not be repeated here.
  • the embodiment of the present invention further provides a communication connection release method, which is performed by a core network, as shown in FIG. 10, the method includes:
  • Step S1001 The core network receiving the monitoring device receives the termination data receiving indication of the carried group identifier when each device in the group reaches the communication connection release condition;
  • Step S1002 The core network initiates a group connection release process, and releases the communication connection of the devices in the group.
  • the monitoring equipment is specifically:
  • the core network initiates a group connection release process, and releases the communication connection of the devices in the group, which specifically includes:
  • the core network releases the internal bearer of the core network of all devices in the group according to the group identifier, and sends a release indication message carrying the group identifier to the base station;
  • the core network receives the release completion message after the base station releases the S1 interface bearer and context of all the devices in the group, and notifies the device in the group to release the RRC connection.
  • the core network initiates a group connection release process, and releases the communication connection of the devices in the group, including:
  • the core network releases the internal bearer of the core network of all the devices in the group according to the group identifier, and sends a release indication message carrying the group identifier to the radio network controller RNC.
  • the core network receives the release completion message after the RNC releases the Iu interface bearer and context of all the devices in the group and notifies the device in the group to release the RRC connection.
  • the core network releases the internal bearer of the core network of all devices in the group according to the group identifier, including:
  • the core network releases the internal bearer of the core network of all devices in the group according to the group identifier and the correspondence between the group identifier and the bearer determined when the bearer is established.
  • the embodiment of the present invention further provides a communication connection release device.
  • the device includes: a determining unit 1101, configured to determine that each device in the group reaches a communication connection release condition;
  • the sending unit 1102 is configured to send, to the core network, a termination data receiving indication that carries the group identifier, where the termination data receiving indication is used to instruct the core network to initiate a group connection release process, and release the communication connection of the devices in the group.
  • the device can be an MTC server, an MTC user, an eNodeB, an RNC or a NodeB.
  • the determining unit is specifically used for:
  • the device when the device is an eNodeB, the device further includes: a first release unit, configured to receive a release indication message of the carried group identifier sent by the core network after releasing the internal bearer of all the devices in the group according to the group identifier; releasing the S1 interface bearer and the context of the devices in all the groups, and notifying The intra-group device performs RRC connection release; and feeds back the release completion message to the core network.
  • a first release unit configured to receive a release indication message of the carried group identifier sent by the core network after releasing the internal bearer of all the devices in the group according to the group identifier; releasing the S1 interface bearer and the context of the devices in all the groups, and notifying The intra-group device performs RRC connection release; and feeds back the release completion message to the core network.
  • the device when the device is an RNC, the device further includes:
  • a second release unit configured to receive a release indication message of the carried group identifier sent by the core network after releasing the internal bearer of all the devices in the group according to the group identifier; releasing the Iu interface bearer and the context of the devices in all the groups, and the notification group
  • the internal device performs RRC connection release; feeds back the release completion message to the core network; or
  • the device when the device is a NodeB, the device further includes:
  • a third release unit configured to receive, after releasing the Iu interface bearer and the context of the devices in all the groups, the notification sent by the RNC releases the Iub interface bearer and context messages of all the devices in the group, and releases the Iub interface bearer of all the devices in the group. And context.
  • the first release unit or the second release unit notifies the device in the group to perform the RRC connection release, and specifically includes: sending an RRC connection release indication to the intra-group device by using the group broadcast mode, and notifying the device in the group to perform the RRC connection release.
  • the first release unit releases the S1 interface bearer and the context of the devices in all the groups, and specifically includes:
  • the second release unit releases the Iu interface bearer and the context of the devices in all the groups, and specifically includes:
  • the Iu interface bearer and context of all devices in the group are released according to the group identifier and the correspondence between the group identifier and the bearer and the context determined when the bearer and the context are established.
  • the embodiment of the present invention further provides a communication connection release device, which may be specifically a core network, as shown in FIG. 12, the device includes:
  • the indication receiving unit 1201 is configured to receive, by the monitoring device, a termination data receiving indication of the carried group identifier that is sent when each device in the group reaches the communication connection release condition;
  • the connection release unit 1202 is configured to initiate a group connection release process, and release a communication connection of devices in the group.
  • connection releasing unit 1202 is specifically configured to:
  • connection releasing unit 1202 is specifically configured to:
  • the connection release unit 1202 releases the internal bearer of the core network of all the devices in the group according to the group identifier, and specifically includes: the core network according to the group identifier and the correspondence between the group identifier and the bearer determined when the bearer is established, and releasing the core network of all devices in the group .
  • the embodiment of the invention further provides a communication connection release system, as shown in FIG. 13, comprising:
  • the monitoring device 1301 is configured to determine that each device in the group reaches a communication connection release condition, and send a termination data receiving indication that carries the group identifier to the core network, where the termination data receiving indication is used to instruct the core network to initiate a group connection release process, and release the group Communication connection of the device;
  • the core network 1302 is configured to receive, by the monitoring device, a termination data receiving indication of the carried group identifier that is sent when each device in the group reaches the communication connection release condition; initiate a group connection release process, and release the communication connection of the devices in the group.
  • the monitoring device 1301 when the monitoring device 1301 is a base station in the LTE network, the monitoring device 1301 is further configured to: receive, after the core network releases the internal bearer of the core network of all devices in the group according to the group identifier, release the carrying group identifier Instructing the message; releasing the S1 interface bearer and the context of the devices in the group, and notifying the device in the group to perform the RRC connection release; and feeding back the release completion message to the core network;
  • the monitoring device 1301 when the monitoring device 1301 is an RNC, the monitoring device 1301 is further configured to:
  • the receiving core network After receiving the internal bearer of the core network of all the devices in the group, the receiving core network sends a release indication message carrying the group identifier, releasing the Iu interface bearer and context of the devices in the group, and notifying the device in the group to perform RRC connection release; Sending a release completion message to the core network;
  • the monitoring device 1301 when the monitoring device 1301 is a base station in the UMTS network, the monitoring device 1301 is further configured to: after receiving the Iu interface bearer and the context of all the devices in the group, the receiving RNC sends a notification to release all the devices in the group.
  • the Iub interface carries the message of the context and releases the Iub interface bearer and the context of the devices in the group.
  • the system further includes: a base station, configured to receive the core After the network releases the internal bearer of the core network of all the devices in the group according to the group identifier, the release indication message of the carried group identifier is sent; the S1 interface bearer and the context of the devices in all the groups are released, and the device in the group is notified to perform RRC connection release; Net feedback release completion message;
  • the system when the monitoring device 1301 is an MTC server or an MTC device, the system further includes: an RNC, configured to receive the bearer group identifier sent after the core network releases the internal bearer of all the devices in the group according to the group identifier.
  • the release indication message release the Iu interface bearer and context of the devices in all groups, and notify the device in the group to perform RRC connection release; and feed back the release completion message to the core network;
  • the core network 1302 initiates a group connection release process, and releases the communication connection of the devices in the group, which specifically includes: Release the internal bearer of the core network of all devices in the group according to the group identifier, and send a release indication message carrying the group identifier to the base station; the receiving base station releases the S1 interface bearer and context of all the devices in the group, and notifies the intra-group device to perform the RRC connection. After release, the feedback release completion message; or
  • the receiving RNC releases the Iu interface bearer and context of all the devices in the group, and notifies the device in the group After the RRC connection is released, the feedback release completion message is sent.
  • An embodiment of the present invention provides a monitoring device. As shown in FIG. 14, the device includes:
  • the first processor 1401 is configured to determine that each device in the group reaches a communication connection release condition
  • the first transmitter 1402 is configured to send, to the core network, a termination data receiving indication that carries the group identifier, where the termination data receiving indication is used to instruct the core network to initiate a group connection release process, and release the communication connection of the devices in the group.
  • the device can be an MTC server, MTC user, eNodeB, RNC or NodeB.
  • the first processor 1401 is specifically configured to:
  • the first processor 1401 is further configured to receive a release indication message of the bearer group identifier that is sent after the core network releases the internal bearer of the core network of all devices in the group according to the group identifier;
  • the S1 interface of all the devices in the group carries the context and the device in the group is notified to release the RRC connection; the release completion message is fed back to the core network.
  • the first processor 1401 when the device is an RNC, is further configured to receive a release indication message of the bearer group identifier that is sent after the core network releases the internal bearer of the core network of all devices in the group according to the group identifier. Release the Iu interface bearer and context of all devices in the group, and notify the device in the group to release the RRC connection; feed back the release completion message to the core network; or
  • the first processor 1401 is further configured to receive, after the RNC releases the Iu interface bearer and the context of all the devices in the group, the notification sent by the Iub interface of all the devices in the group is released. Host and context messages, and release the Iub interface bearer and context of all devices in the group.
  • the first processor 1401 notifies the device in the group to perform the RRC connection release, which specifically includes:
  • the RRC connection release indication is sent to the intra-group device by the group broadcast mode, and the device in the group is notified to perform RRC connection release.
  • the first processor 1401 is further configured to release the S1 interface bearer and the context of the devices in all the groups, and the method includes: releasing all the devices in the group according to the group identifier and the correspondence between the group identifier and the bearer and the context determined when the bearer and the context are established.
  • S 1 interface bearer and context The first processor 1401 is further configured to put the Iu interface bearer and the context of the devices in all the groups, and specifically includes: releasing all the devices in the group according to the group identifier and the correspondence between the group identifier and the bearer and the context determined when the bearer and the context are established. Iu interface bearer and context.
  • the embodiment of the invention provides a core network device device. As shown in FIG. 15, the device includes:
  • a second transmitter 1501 configured to receive, by the monitoring device, a termination data receiving indication of the carried group identifier that is sent when each device in the group reaches a communication connection release condition;
  • the second processor 1502 is configured to initiate a group connection release process, and release a communication connection of devices in the group.
  • the second processor 1502 is specifically configured to:
  • the second processor 1502 is specifically configured to:
  • the receiving RNC releases the Iu interface bearer and context of all the devices in the group, and notifies the device in the group After the RRC connection is released, the feedback release completion message is sent.
  • the second processor 1502 releases the internal bearer of the core network of all the devices in the group according to the group identifier, and specifically includes: the core network releases the internal network of all the devices in the group according to the group identifier and the correspondence between the group identifier and the bearer determined when the bearer is established. Hosted.
  • the embodiment of the invention provides a communication connection release method, device and system.
  • the device is uniformly released, thereby avoiding separate release of each device, thereby reducing Interface signaling and air interface signaling load improve the efficiency of communication connection release.
  • embodiments of the present invention can be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware. Moreover, the present invention can be embodied in the form of a computer program product embodied on one or more computer-usable storage interfaces (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer usable program code.
  • computer-usable storage interfaces including but not limited to disk storage, CD-ROM, optical storage, etc.
  • the present invention has been described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (system), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flowchart illustrations and/or FIG.
  • the computer program instructions can be provided to a first processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing device to produce a machine for execution by a first processor of a computer or other programmable data processing device Finger Means for generating the functions specified in one or more of the flow or in a single block or blocks of a flow diagram.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

Landscapes

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

Description

一种通信连接释放方法、 装置及系统
本申请要求在 2012年 8月 29日提交中国专利局、 申请号为 201210312494.8、 发明名 称为"一种通信连接释放方法、 装置及系统"的中国专利申请的优先权， 其全部内容通过引 用结合在本申请中。
技术领域
本发明涉及通信技术， 尤其涉及一种通信连接释放方法、 装置及系统。 背景技术
M2M ( Machine to Machine, 机器到机器）通信是未来智能化发展的一种趋势。 在第 三代移动通信系统以及其长期演进系统中需要支持 MTC ( Machine Type Communications, 机器类型通信）功能。 其中 Smart Metering (智能电表）作为一种典型的 MTC应用场景得 到了广泛的关注。 Smart Metering业务具有分布密度高、 网络对设备的控制需求低、 设备 上 ·ί艮业务的时间周期长， 业务上 ·ί艮时间集中、 应用单一及位置固定等特点， 而且集中时间 上报相关的业务数据是主要的通信方式。
MTC实现了将多种不同类型的通信技术有机结合， 如： 机器对机器通信、机器控制通 信、 人机交互通信、 移动互联通信， 从而推动社会生产和生活方式的发展。 有时， MTC通 信又称为 Μ2Μ ( Machine-to-machine, 机器间）通信或物联网。
当前的移动通信网络是针对人与人之间的通信设计的， 例如： 网络容量即是针对人与 人之间的通信设计的。如果希望利用移动通信网络来支持 MTC通信就需要根据 MTC通信 的特点对移动通信系统的机制进行优化， 以便能够在对传统的人与人通信不受或受较小影 响的情况下， 更好地实现 MTC通信。
当前认识到的 MTC通信可能存在的一些特点有： MTC设备具有低移动性； MTC设 备与网络侧进行数据传输的时间是可控的； MTC网络与网络侧进行的数据传输对数据传输 对实时性要求不高， 即： 具有时间容忍性； MTC设备能量受限， 要求极低的功率消耗； MTC设备和网络侧之间只进行小数据量的信息传输； MTC设备可以以组为单位进行管理。
通常， 一个 MTC设备可以具有上述的一个或多个特点。
目前普遍应用的 UMTS ( Universal Mobile Telecommunication System,通用移动通信系 统） 系统网络架构如图 1所示， UMTS系统由核心网、 RNC ( Radio Network Controller, 无线网络控制器）、 B ( NodeB , 基站）及 UE ( User Equipment, 设备， 即设备）组成， 其中 UE与 NB之间通过空中接口（ Uu接口）进行通信 , B与 RNC组成 RAN( Radio Access Network , 无线接入网）， 二者之间通过 lub接口通信， RAN与核心网之间通过 Iu接口进 行通信。
在设备需要与网络进行通信时， 通过一系列交互流程实现通信连接的建立， 包括空口 链路建立（ RRC连接）、 lub接口无线链路建立以及 lu接口通信连路的建立，其中 RRC( Radio Resource Connection , 无线资源连接 )连接及 lu接口连接是针对每个 UE建立的， 主要用 于在网络的不同节点维护设备的上下文。 当完成通信过程后， 相关的通信链接需要进行释 放。 目前 3GPP ( 3rd Generation Partnership Project, 第三代移动通信标准化组织 )标准中 定义的通信连接释放流程如图 2所示， 其中， 释放过程可以由 RAN触发， 也可以由核心 网发起。 如果由核心网触发， 则图 2中的第一条消息 Iu release request ( lu释放请求）不需 要出现。 具体的过程如下：
步骤 S201、 对于 RAN触发的场景， RAN检测到针对设备的 RRC连接已经被释放， 或者检测到需要释放无线资源， 则向 SGSN ( Serving GPRS Support Node, 服务 GPRS支 持节点； GPRS , General Packet Radio Service, 通用分组无线业务 )发送 lu Release Request ( lu释放请求） 消息。
步骤 S202、 SGSN通过向 RAN发送 lu Release Command ( lu释放指令） 消息进行 lu 接口连接释放；
步骤 S203、 RNC向设备 ( MS )发起 RRC连接释放消息触发 RRC连接释放过程； 步骤 S204、 设备进行 RRC连接释放相关处理， 完成后设备向 RAN反馈 RRC连接释 放完成消息；
步骤 S205、 RNC向 NodeB发起无线链路释放消息（ Radio Link Deletion )消息触发 lub 承载及上下文释放过程；
步骤 S206、NodeB向 RNC返回无线链路释放响应消息（ Radio Link Deletion Response ) 消息；
步骤 S207、 RAN通过向 SGSN发送 lu Release Completion ( lu释放完成 )消息进行确 认。
通过上述步骤， 即可完成对设备的连接释放。
在 LTE ( Long Term Evolution, 长期演进） 系统中， 也存在设备的释放， 具体的， LTE 系统网络架构如图 3所示， LTE系统由核心网、 e B (基站）及 UE、组成，其中 UE与 e B 之间通过空中接口 （ Uu接口）进行通信， eNB与核心网之间通过 S 1接口进行通信。
对于通信连接建立和释放过程， LTE系统与 UMTS系统类似， 具体的通信连接释放过 程如图 4所示。
基于组的通信方式作为在特定场景下的解决方案， 能够有效降低系统信令负荷。 在很 多应用场景中， MTC通信都会涉及到一组设备， 如水表， 电表， 煤气表等行业应用， 一定 区域范围内的水、 电、 煤气表设备可以属于一个 MTC user/MTC server (水、 电、 煤气公司 的管理平台）， 而无论是从 MTC user的角度还是从运营商的角度， 基于一个组整体进行管 理都是有好处的。 比如， 当 MTC user需要对所拥有的 MTC设备发送公共信息或需要寻呼 专用信令发送相同的信息内容， 就会造成一定程度的资源浪费， 而如果能够基于组进行触 发或发送相同数据， 将会大大减少信令开销， 提高资源利用率。 从运营商角度， 则能够针 对一组设备进行基于组的计费等， 便于管理。
但是， 通信连接的释放都是针对一个设备而言的， 而在基于组的通信中， 组内设备集 中完成数据传输后， 如果釆用每个设备分别释放连接的方式， 则会导致的 Sl/Iu接口信令 及空口信令负荷较大， 同时通信连接释放的效率也较低。 发明内容
本发明实施例提供一种通信连接释放方法、 装置及系统， 以减少接口信令和空口信令 负荷， 提高通信连接释放的效率。
一种通信连接释放方法， 包括：
确定组内每个设备均达到通信连接释放条件；
向核心网发送携带组标识的终止数据接收指示， 所述终止数据接收指示用于指示所述 核心网发起组连接释放过程， 释放组内设备的通信连接。
一种通信连接释放方法， 包括：
核心网接收监测设备在确定组内每个设备均达到通信连接释放条件时， 发送的携带组 标识的终止数据接收指示；
核心网发起组连接释放过程， 释放组内设备的通信连接。
一种通信连接释放装置， 包括：
确定单元， 用于确定组内每个设备均达到通信连接释放条件；
发送单元， 用于向核心网发送携带组标识的终止数据接收指示， 所述终止数据接收指 示用于指示所述核心网发起组连接释放过程， 释放组内设备的通信连接。
一种通信连接释放装置， 包括：
指示接收单元， 用于接收监测设备在确定组内每个设备均达到通信连接释放条件时， 发送的携带组标识的终止数据接收指示；
连接释放单元， 用于发起组连接释放过程， 释放组内设备的通信连接。 一种通信连接释放系统， 包括：
监测设备， 用于确定组内每个设备均达到通信连接释放条件； 向核心网发送携带组标 识的终止数据接收指示， 所述终止数据接收指示用于指示所述核心网发起组连接释放过 程， 释放组内设备的通信连接；
核心网， 用于接收监测设备在确定组内每个设备均达到通信连接释放条件时， 发送的 携带组标识的终止数据接收指示； 发起组连接释放过程 , 释放组内设备的通信连接。
本发明实施例提供一种通信连接释放方法、 装置及系统， 在组内每个设备均达到通信 连接释放条件时， 对该组设备统一进行释放， 避免了对每个设备分别进行释放， 减少了接 口信令和空口信令负荷， 提高了通信连接释放的效率。 附图说明
图 1为背景技术中 UMTS系统网络结构示意图；
图 2为背景技术中 UMTS系统通信连接释放流程图；
图 3为背景技术中 LTE系统网络结构示意图；
图 4为背景技术中 LTE系统通信连接释放流程图；
图 5为本发明实施例提供的通信连接释放方法流程图之一；
图 6为本发明实施例中对应于实施例一的通信连接释放方法流程图；
图 7为本发明实施例中对应于实施例二的通信连接释放方法流程图；
图 8为本发明实施例中对应于实施例三的通信连接释放方法流程图；
图 9为本发明实施例中对应于实施例四的通信连接释放方法流程图；
图 10为本发明实施例提供的通信连接释放方法流程图之二；
图 11为本发明实施例提供的通信连接释放装置结构示意图之一；
图 12为本发明实施例提供的通信连接释放装置结构示意图之二；
图 13为本发明实施例提供的通信连接释放系统结构示意图；
图 14为本发明实施例提供的监测设备结构示意图之一；
图 15为本发明实施例提供的核心网设备结构示意图之二。 具体实施方式
本发明实施例提供一种通信连接释放方法、 装置及系统， 在组内每个设备均达到通信 连接释放条件时， 对该组设备统一进行释放， 避免了对每个设备分别进行释放， 减少了接 口信令和空口信令负荷， 提高了通信连接释放的效率。 如图 5所示， 本发明实施例提供的通信连接释放方法包括：
步骤 S501、 确定组内每个设备均达到通信连接释放条件；
步骤 S502、 向核心网发送携带组标识的终止数据接收指示， 终止数据接收指示用于指 示核心网发起组连接释放过程， 释放组内设备的通信连接。
其中， 确定组内每个设备均达到通信连接释放条件， 具体包括： 确定组内每个设备完 成数据交互； 或者确定预设的定时器超时。
该通信连接释放方法可以由 MTC server ( MTC服务器）或者 MTC user ( MTC设备 ) 执行， 也可以由 LTE网络中的 eNodeB ( e B , 演进基站）执行， 还可以由 UMTS网络中 的 RNC或者 NodeB (基站）执行。
在步骤 S502中，核心网接收到终止数据接收指示，核心网通过 Iu ( UMTS ) /SI ( LTE ) 接口向 RNC ( UMTS ) /eNB ( LTE )发起一条携带组标识（ Group ID )的 Iu/Sl组连接指示 触发组连接释放过程， RNC ( UMTS ) /eNB ( LTE )接收到该指示后， 释放所有组内设备 的 Iu/Sl相关上下文， 并通过组广播的方式通知组内设备进行 RRC连接释放， 并向核心网 反馈 Iu/S 1组连接释放完成； 设备读取到 RRC连接释放指示后进行无线资源的释放过程 , 无需向网络反馈。
需要特别说明的是,对于目前的 Iu/Sl连接建立过程，需要每个设备都建立独立的 Iu/Sl 承载及上下文，因此通过一条 Iu/Sl组连接指示触发一组 Iu/Sl连接的释放过程，需要 RNC ( UMTS ) /eNB ( LTE )预先确定 Iu/Sl承载及上下文和组的对应关系， 一种可能的解决方 法是在对每个设备进行 Iu/Sl连接建立时， 就通知 RNC ( UMTS ) /eNB ( LTE )该连接所 属的组标识信息， 则当 RNC ( UMTS ) /eNB ( LTE )收到携带组标识（ Group ID )的 Iu/Sl 组连接释放指示时， 就能够释放所有组内设备的 Iu/Sl相关承载及上下文。
另一个需要指出的是， 对于 UMTS系统， 还涉及到 lub接口承载的释放过程， 此时， 也可以釆用 lub承载组释放的方式。 即， 通过一条 lub组连接指示触发一组 lub连接的释 放过程， 同样的， 需要 NodeB预先确定 lub承载及上下文和组的对应关系， 一种可能的解 决方法是在对每个设备进行 lub连接建立时（ B AP： 无线连接建立过程）， 就通知 NodeB 该连接所属的组标识信息， 则当 NodeB收到携带组标识（ Group ID ) 的 lub组连接释放指 示时， 就能够释放所有组内设备的 lub相关承载及上下文。
下面通过具体的实施例对各网络中的通信连接释放进行具体说明：
实施例一、
该实施例为在 LTE网络中， 由 MTC server或者 MTC user触发组连接释放。
此时， 核心网发起组连接释放过程， 释放组内设备的通信连接， 具体包括： 核心网根据组标识释放组内所有设备的核心网内部承载（即 S11接口（MME和 Serving
GW之间的接口）设备承载）， 并向基站发送携带组标识的释放指示消息；
基站在接收到释放指示消息后， 释放所有组内设备的 S1 接口承载及上下文， 并通知 组内设备进行 RRC连接释放；
基站向核心网反馈释放完成消息。
其中， 为进一步节省信令， 减少网络负担， 在通知组内设备进行 RRC 连接释放时， 可以通过组广播方式向组内设备发送 RRC连接释放指示， 通知组内设备进行 RRC连接释 放； 设备接收到 RRC 连接释放指示后， 进行无线资源的释放过程， 释放完毕后， 无需进 行反馈， 从而更进一步减少网络负担。
核心网能够根据组标识确定组内设备的承载并进行释放， 可以在建立承载时， 核心网 就确定组标识和承载的对应关系， 这样， 在需要释放承载时， 核心网即可核心网根据组标 识以及建立承载时确定的组标识和承载的对应关系， 释放组内所有设备的核心网内部承 载。
同样的， 也可以在建立承载时， 基站就确定组标识和承载的对应关系， 这样， 在需要 释放承载时， 基站也可以根据组标识以及建立承载及上下文时确定的组标识和承载及上下 文的对应关系， 释放所有组内设备的 S1接口承载及上下文。
具体的， 如图 6所示， LTE网络中， 由 MTC server或者 MTC user触发组连接释放的 释放过程包括：
步骤 S601、 MTC server或者 MTC user确定组内每个设备均达到通信连接释放条件 , 向核心网中的 MTC IWF ( Interworking Functionality, 互操作实体 )实体发送终止数据接收 指示， 该指示中包含标识组的 Group ID (组标识）等信息；
此时， MTC server或者 MTC user需要进行组内设备数据上报情况的检测， 具体的检 测手段可以是： 判断组内设备数据释放都已经接收到， 或者有部分设备数据未接收到但已 超过预设的等待定时器。
步骤 S602、 MTC IWF向 MME ( Mobility Management Element, 移动管理实体）发送 终止数据传输指示， 其中包含组标识等信息； 该终止数据传输指示可以通过新定义的消息 发送， 也可以在现有的消息中增加相关的信息， 实现终止数据传输指示的发送；
步骤 S603、 MME向 Serving GW (服务网关）发送 Release Group Access Bearer Request (释放组连接承载请求）， 该请求中携带组标识；
步骤 S604、 Serving GW根据释放组连接承载请求中携带的 Group ID, 释放组内设备 相关的 S 11接口用户面承载； 具体的， 可以在 Serving GW建立组内设备承载的时候就通 过组标识等信息标识出该承载所属的组， 当 Serving GW收到携带组标识的释放组连接承 载请求时， Serving GW即可将标识为属于该组的承载都进行释放；
步骤 S605、 Serving GW向 MME返回 Release Group Access Bearer Response (释放组 连接承载响应 ) 消息；
步骤 S606、 MME向 eNB发送 S1AP消息 SI group Context Release Command ( SI组 连接释放指令）， 该消息中携带 Group ID, 发起组内设备的 S1承载及上下文的释放过程。 需要特别说明的是， 如果在 RAN ( Radio Access Network, 无线接入网） sharing ( RAN共 享）场景（即多个 PLMN ( Public Land Mobile Network, 公共陆地移动网络 )共享 RAN资 区分组，此时， S 1 group Context Release Command消息中需要携带 PLMN ID指示 Group ID 所属的 PLMN;
步骤 S607、 eNB接收到携带 Group ID的 SI group Context Release Command消息后， 释放 Group ID所标识的组中所有设备的 S1承载及上下文；需要特别说明的是，可以在 eNB 建立组内设备 S1承载及上下文的时候就通过 INITIAL CONTEXT SETUP REQUEST (初始 连接建立请求）消息中携带的如 Group ID等信息标识出所建立的承载所属的 Group, 从而 使得收到携带 Group ID的 SI group Context Release Command消息时， eNB将属于该 Group 的承载及上下文都进行释放； 其中， SI group Context Release Command消息可以是新定义 的 S1AP消息， 也可以是对现有的 SI Context Release Command ( SI连接释放指令） 消息 进行修改， 增加 group ID等相关信息。
步骤 S608、 eNB向组内设备发送 RRC连接释放指示，组内设备接收到该 RRC连接释 放指示后，若根据 RRC连接释放指示中携带的 Group ID等信息确定是自己所属组的消息， 则进行 RRC 连接释放， 删除存储的上下文及资源配置等信息。 从减少空口信令负荷的角 度， 该 RRC连接释放指示可以通过组广播的方式通知组内设备， 具体而言， "组广播" 方 式可以是通过 G-RNTK Group Radio Network Temporary Identity,组无线网络临时标识）（预 先设定的所有具有组特性的设备都需要监听的标识）加扰的 PDCCH ( Physical Downlink Control Channel, 物理下行控制信道）调度组内设备去读取 PDSCH ( Physical Downlink Shared Channel, 物理下行共享信道）信息中携带的 RRC connection Release ( RRC连接释 放）指示， 其中 RRC connection Release指示中包含 Group ID , 当设备解读消息中的 Group ID为自己所属的组后， 进行 RRC连接释放， 完成连接释放后无需向网络进行反馈。 需要 特别说明的是， 在 RAN sharing场景下， RRC 连接释放指示中可以携带 PLMN ID指示 Group ID所属的 PLMN。 步骤 S609、 e B向组内设备发送 RRC 连接释放指示后， 同时删除所存储的组内设备 的 RRC相关上下文信息及相关的配置信息，并通过 S1AP消息 SI Context Release Complete ( SI连接释放完成）向 MME通知组内连接释放完成。 需要说明的是， 其中该消息可以是 新定义的 S1AP消息， 也可以是在目前的 SI RELEASE COMPLETE ( SI释放完成） 消息 中增加如 Group ID等信息。
实施例二、
在 LTE网络中， 由 eNB触发组连接释放。
此时， 核心网发起组连接释放过程， 释放组内设备的通信连接， 具体包括： 核心网根据组标识释放组内所有设备的核心网内部承载（即 S11接口（MME和 Serving GW之间的接口）设备承载）， 并向基站发送携带组标识的释放指示消息；
基站在接收到释放指示消息后， 释放所有组内设备的 S1 接口承载及上下文， 并通知 组内设备进行 RRC连接释放；
基站向核心网反馈释放完成消息。
同样的， 为进一步节省信令， 减少网络负担， 在通知组内设备进行 RRC连接释放时， 可以通过组广播方式向组内设备发送 RRC连接释放指示， 通知组内设备进行 RRC连接释 放； 设备接收到 RRC 连接释放指示后， 进行无线资源的释放过程， 释放完毕后， 无需进 行反馈， 从而更进一步减少网络负担。
核心网能够根据组标识确定组内设备的承载并进行释放， 可以在建立承载时， 核心网 就确定组标识和承载的对应关系， 这样， 在需要释放承载时， 核心网即可核心网根据组标 识以及建立承载时确定的组标识和承载的对应关系， 释放组内所有设备的核心网内部承 载。
同样的， 也可以在建立承载时， 基站就确定组标识和承载的对应关系， 这样， 在需要 释放承载时， 基站也可以根据组标识以及建立承载及上下文时确定的组标识和承载及上下 文的对应关系， 释放所有组内设备的 S1接口承载及上下文。
具体的， 如图 7所示， LTE网络中， 由 eNB触发组连接释放的释放过程包括： 步骤 S701、 eNB确定组内每个设备均达到通信连接释放条件 , 向核心网中的 MME发 送终止数据接收指示， 该指示中包含标识组的 Group ID (组标识）等信息；
此时， 由 eNB进行组内设备数据上报情况的检测， 具体的检测手段可以是： 根据接收 到的组内设备上报数和预先从 MME获得的组内设备数进行对比，其中 eNB需要确定属于 组内设备的数据， 因此需要组内设备上报数据时携带 eNB可见的 Group ID, 同时可以结合 预设的等待定时器等方式； 或者 eNB进行组内设备的活跃性检测， 当发现一段时间内没有 组内设备数据上报， 则可以判断组内设备数据上报完成。 当检测到组内设备数据完成接收 后， e B通过 S1AP消息： SI group Context Release Request ( SI组连接释放请求）请求 MME释放与该组相关的承载及上下文， 该消息中需要包含 Group ID信息。 其中， Iu group Context Release Request可以是新定义的 SI AP消息，也可以是对 SI Context Release Request ( SI连接释放请求） 消息中增加 Group ID的信息。
步骤 S702-步骤 S708与实施例一中步骤 S603-步骤 S609相同， 在此不再重复叙述。 实施例三、
该实施例为在 UMTS网络中， 由 MTC server或者 MTC user触发组连接释放。
此时， 核心网发起组连接释放过程， 释放组内设备的通信连接， 具体包括： 核心网根据组标识释放组内所有设备的核心网内部承载（即 Gp接口（ SGSN和 GGSN 之间的接口）设备承载）， 并向无线网络控制器 RNC发送携带组标识的释放指示消息；
RNC在接收到释放指示消息后， 释放所有组内设备的 Iu接口承载及上下文， 以及通 知组内设备进行 RRC连接释放；
RNC向核心网反馈释放完成消息。
如涉及 Iub接口的释放过程， 则 RNC释放所有组内设备的 Iu接口承载及上下文后， 还包括：
RNC通知基站释放所有组内设备的 Iub接口承载及上下文。
其中， 为进一步节省信令， 减少网络负担， 在通知组内设备进行 RRC 连接释放时， 可以通过组广播方式向组内设备发送 RRC连接释放指示， 通知组内设备进行 RRC连接释 放； 设备接收到 RRC 连接释放指示后， 进行无线资源的释放过程， 释放完毕后， 无需进 行反馈， 从而更进一步减少网络负担。
核心网能够根据组标识确定组内设备的承载并进行释放， 可以在建立承载时， 核心网 就确定组标识和承载的对应关系， 这样， 在需要释放承载时， 核心网即可核心网根据组标 识以及建立承载时确定的组标识和承载的对应关系， 释放组内所有设备的核心网内部承 载。
同样的， 也可以在建立承载时， RNC就确定组标识和承载的对应关系， 这样， 在需要 释放承载时， RNC也可以根据组标识以及建立承载及上下文时确定的组标识和承载及上下 文的对应关系， 释放所有组内设备的 Iu接口承载及上下文。
具体的， 如图 8所示， UMTS网络中， 由 MTC server或者 MTC user触发组连接释放 的释放过程包括：
步骤 S801、 MTC server或者 MTC user确定组内每个设备均达到通信连接释放条件 , 向核心网中的 MTC IWF实体发送终止数据接收指示，该指示中包含标识组的 Group ID(组 标识）等信息；
此时， MTC server或者 MTC user需要进行组内设备数据上报情况的检测， 具体的检 测手段可以是： 判断组内设备数据释放都已经接收到， 或者有部分设备数据未接收到但已 超过预设的等待定时器。
步骤 S802、 MTC IWF向 SGSN发送终止数据传输指示， 其中包含组标识等信息； 该 终止数据传输指示可以通过新定义的消息发送， 也可以在现有的消息中增加相关的信息， 实现终止数据传输指示的发送；
步骤 S803、 SGSN向 GGSN ( Gateway GPRS Support Node, 网关 GPRS支持节点）发 送 Release Group Access Bearer Request (释放组连接承载请求）， 该请求中携带组标识； 步骤 S804、 GGSN根据释放组连接承载请求中携带的 Group ID,释放组内设备相关的 核心网内部 Gp接口用户面承载； 具体的， 可以在 GGSN建立组内设备承载的时候就通过 组标识等信息标识出该承载所属的组，当 GGSN收到携带组标识的释放组连接承载请求时， GGSN即可将标识为属于该组的承载都进行释放；
步骤 S805、 GGSN向 SGSN返回 Release Group Access Bearer Response (释放组连接 承载响应） 消息；
步骤 S806、 SGSN向 RNC发送 RANAP消息 Iu group Context Release Command ( Iu 组连接释放指令），该消息中携带 Group ID,发起组内设备的 Iu承载及上下文的释放过程。 需要特别说明的是， 如果在 RANsharing ( RAN共享）场景下， 由于可能不同的 PLMN下 会出现相同的 Group ID导致 RAN侧无法根据 Group ID区分组， 此时， Iu group Context Release Command消息中需要携带 PLMN ID指示 Group ID所属的 PLMN;
步骤 S807、 RNC接收到携带 Group ID的 Iu group Context Release Command消息后， 释放 Group ID所标识的组中所有设备的 Iu承载及上下文；需要特别说明的是，可以在 RNC 建立组内设备 Iu承载及上下文的时候就通过 RAB ASSIGNMENT REQUEST (无线接入承 载分配请求， RAB, Radio Access Bearer, 无线接入承载） 消息中携带的如 Group ID等信 息标识出所建立的承载所属的 Group, 从而使得收到携带 Group ID 的 Iu group Context Release Command消息时， RNC将属于该 Group的承载及上下文都进行释放；其中， Iu group Context Release Command 消息可以是新定义的 S1AP 消息， 也可以是对现有的 RAB ASSIGNMENT REQUEST消息进行修改， 增加 group ID等相关信息。
步骤 S808、 RNC向组内设备发送 RRC连接释放指示， 组内设备接收到该 RRC连接 释放指示后， 若根据 RRC连接释放指示中携带的 Group ID等信息确定是自己所属组的消 息， 则进行 RRC 连接释放， 删除存储的上下文及资源配置等信息。 从减少空口信令负荷 的角度，该 RRC连接释放指示可以通过组广播的方式通知组内设备，具体而言， "组广播" 方式可以是通过 G-RNTI (预先设定的所有具有组特性的设备都需要监听的标识）加扰的 HS-SCCH ( High Speed Shared Control Channel , 高速共享控制信道）调度组内设备去读取 HS-PDSCH ( High Speed Physical Downlink Shared Channel , 高速物理下行共享信道）信息 中携带的 RRC connection Release ( RRC连接释放）指示， 其中 RRC connection Release指 示中包含 Group ID , 当设备解读消息中的 Group ID为自己所属的组后， 进行 RRC连接释 放， 完成连接释放后无需向网络进行反馈。 需要特别说明的是， 在 RAN sharing场景下， RRC 连接释放指示中可以携带 PLMN ID指示 Group ID所属的 PLMN。
步骤 S809、 RNC向组内设备发送 RRC连接释放指示后， RRC删除所存储的组内设备 的 RRC相关上下文信息及相关的配置信息， 并向 NodeB发送 Iub group Context Release Command ( Iub组连接释放指令 ) 消息； 该 Iub Group Context Release Command消息可以 是新定义的 B AP( NodeB Application Part ,基站应用部分）消息，也可以是对现有的 RADIO LINK SETUP REQUEST (无线链路建立请求） 消息进行修改， 增加 group ID等相关信息 元素
步骤 S810、 NodeB释放组内所有设备的 Iub承载及上下文； 同样的， 可以在 NodeB 建立组内设备 Iub 承载及上下文的时候就通过在 BAP 过程的 RADIO LINK SETUP REQUEST消息 （RNC发给 NodeB ) 中携带的如 Group ID等信息标识出所建立的承载所 属的 Group , 从而使得收到携带 Group ID的 Iub组连接释放消息时， RNC将属于该 Group 的承载及上下文都进行释放。
步骤 S811、 NodeB向 RNC返回 Iub Group Context Release Response ( Iub组连接释放 响应） 消息；
步骤 S812、 RNC通过 RANAP消息 IuContext Release Complete ( Iu连接释放完成）向 MME通知组内连接释放完成。 需要说明的是， 其中该消息可以是新定义的 RANAP消息， 也可以是在目前的 Iu RELEASE COMPLETE ( Iu释放完成 ) 消息中增加如 Group ID等信 息。
实施例四、
该实施例为在 UMTS网络中， 由 RNC或者 NodeB触发组连接释放。
此时， 核心网发起组连接释放过程， 释放组内设备的通信连接， 具体包括： 核心网根据组标识释放组内所有设备的核心网内部承载（即 Gp接口（ SGSN和 GGSN 之间的接口）设备承载）， 并向无线网络控制器 RNC发送携带组标识的释放指示消息； RNC在接收到释放指示消息后， 释放所有组内设备的 Iu接口承载及上下文， 以及通 知组内设备进行 RRC连接释放；
RNC向核心网反馈释放完成消息。
如涉及 Iub接口的释放过程， 则 RNC释放所有组内设备的 Iu接口承载及上下文后， 还包括：
RNC通知基站释放所有组内设备的 Iub接口承载及上下文。
其中， 为进一步节省信令， 减少网络负担， 在通知组内设备进行 RRC 连接释放时， 可以通过组广播方式向组内设备发送 RRC连接释放指示， 通知组内设备进行 RRC连接释 放； 设备接收到 RRC 连接释放指示后， 进行无线资源的释放过程， 释放完毕后， 无需进 行反馈， 从而更进一步减少网络负担。
核心网能够根据组标识确定组内设备的承载并进行释放， 可以在建立承载时， 核心网 就确定组标识和承载的对应关系， 这样， 在需要释放承载时， 核心网即可核心网根据组标 识以及建立承载时确定的组标识和承载的对应关系， 释放组内所有设备的核心网内部承 载。
同样的， 也可以在建立承载时， RNC就确定组标识和承载的对应关系， 这样， 在需要 释放承载时， RNC也可以根据组标识以及建立承载及上下文时确定的组标识和承载及上下 文的对应关系， 释放所有组内设备的 Iu接口承载及上下文。
具体的， 如图 9所示， UMTS网络中， 由 RNC触发组连接释放的释放过程包括： 步骤 S901、 RNC确定组内每个设备均达到通信连接释放条件 , 向核心网中的 SGSN 发送终止数据接收指示， 该指示中包含标识组的 Group ID (组标识）等信息；
此时， 由 RNC进行组内设备数据上报情况的检测， 具体的检测手段可以是： 根据接 收到的组内设备上报数和预先从 SGSN获得的组内设备数进行对比， 其中 RNC需要确定 属于组内设备的数据， 因此需要组内设备上报数据时携带 RNC可见的 Group ID, 同时可 以结合预设的等待定时器等方式； 或者 RNC进行组内设备的活跃性检测， 当发现一段时 间内没有组内设备数据上报， 则可以判断组内设备数据上报完成。 当检测到组内设备数据 完成接收后 , RNC通过 RANAP消息： Iu group Context Release Request ( Iu组连接释放请 求）请求 SGSN释放与该组相关的承载及上下文，该消息中需要包含 Group ID信息。其中， Iu group Context Release Request可以是新定义的 RANAP消息， 也可以是对 Iu Release Request ( Iu释放请求 ) 消息中增加 Group ID的信息。
同样的， 该步骤也可以由 NodeB执行。
步骤 S902-步骤 S911与实施例三中的步骤 S803-步骤 S812相同， 在此不再重复叙述。 本发明实施例还提供一种通信连接释放方法， 该方法由核心网执行， 如图 10 所示， 该方法包括：
步骤 S 1001、 核心网接收监测设备在确定组内每个设备均达到通信连接释放条件时， 发送的携带组标识的终止数据接收指示；
步骤 S 1002、 核心网发起组连接释放过程， 释放组内设备的通信连接。
其中， 监测设备具体为：
机器类通信 MTC服务器； 或者 MTC设备； 或者无线网络控制器 RNC; 或者基站。 对应于实施例一和实施例二， 在 LTE网络中， 核心网发起组连接释放过程， 释放组内 设备的通信连接， 具体包括：
核心网根据组标识释放组内所有设备的核心网内部承载， 并向基站发送携带组标识的 释放指示消息；
核心网接收基站在释放所有组内设备的 S 1 接口承载及上下文， 并通知组内设备进行 RRC连接释放后 , 反馈的释放完成消息；
对应于实施例三和实施例四， 在 UMTS网络中， 核心网发起组连接释放过程， 释放组 内设备的通信连接， 具体包括：
核心网根据组标识释放组内所有设备的核心网内部承载， 并向无线网络控制器 RNC 发送携带组标识的释放指示消息；
核心网接收 RNC在释放所有组内设备的 Iu接口承载及上下文， 以及通知组内设备进 行 RRC连接释放后 , 反馈的释放完成消息。
核心网根据组标识释放组内所有设备的核心网内部承载， 具体包括：
核心网根据组标识以及建立承载时确定的组标识和承载的对应关系， 释放组内所有设 备的核心网内部承载。
相应的， 本发明实施例还提供一种通信连接释放装置， 如图 11所示， 该装置包括： 确定单元 1101 , 用于确定组内每个设备均达到通信连接释放条件；
发送单元 1102 , 用于向核心网发送携带组标识的终止数据接收指示， 终止数据接收指 示用于指示核心网发起组连接释放过程 , 释放组内设备的通信连接。
该装置可以为 MTC server, MTC user、 eNodeB , RNC或者 NodeB。
其中， 确定单元具体用于：
确定组内每个设备完成数据交互； 或者
确定预设的定时器超时。
对应于实施例二， 当该装置为 eNodeB时， 该装置还包括： 第一释放单元， 用于接收核心网根据组标识释放组内所有设备的核心网内部承载后， 发送的携带组标识的释放指示消息； 释放所有组内设备的 S 1 接口承载及上下文， 并通知 组内设备进行 RRC连接释放； 向核心网反馈释放完成消息。
对应于实施例四， 当该装置为 RNC时， 该装置还包括：
第二释放单元， 用于接收核心网根据组标识释放组内所有设备的核心网内部承载后， 发送的携带组标识的释放指示消息； 释放所有组内设备的 Iu接口承载及上下文， 以及通知 组内设备进行 RRC连接释放； 向核心网反馈释放完成消息； 或者
对应于实施例四， 当该装置为 NodeB时， 该装置还包括：
第三释放单元， 用于接收 RNC在释放所有组内设备的 Iu接口承载及上下文后， 发送 的通知释放所有组内设备的 Iub接口承载及上下文的消息， 并释放所有组内设备的 Iub接 口承载及上下文。
其中， 第一释放单元或第二释放单元通知组内设备进行 RRC连接释放 , 具体包括： 通过组广播方式向组内设备发送 RRC连接释放指示， 通知组内设备进行 RRC连接释 放。
第一释放单元释放所有组内设备的 S 1接口承载及上下文， 具体包括：
根据组标识以及建立承载及上下文时确定的组标识和承载及上下文的对应关系， 释放 所有组内设备的 S 1接口承载及上下文；
第二释放单元释放所有组内设备的 Iu接口承载及上下文， 具体包括：
根据组标识以及建立承载及上下文时确定的组标识和承载及上下文的对应关系， 释放 所有组内设备的 Iu接口承载及上下文。
本发明实施例还提供一种通信连接释放装置， 该装置可以具体为核心网， 如图 12 所 示， 该装置包括：
指示接收单元 1201 ,用于接收监测设备在确定组内每个设备均达到通信连接释放条件 时， 发送的携带组标识的终止数据接收指示；
连接释放单元 1202 , 用于发起组连接释放过程， 释放组内设备的通信连接。
其中， 对应于实施例一和实施例二， 连接释放单元 1202具体用于：
根据组标识释放组内所有设备的核心网内部承载， 并向基站发送携带组标识的释放指 示消息；接收基站在释放所有组内设备的 S 1接口承载及上下文，并通知组内设备进行 RRC 连接释放后， 反馈的释放完成消息； 或者
对应于实施例三和实施例四， 连接释放单元 1202具体用于：
根据组标识释放组内所有设备的核心网内部承载， 并向无线网络控制器 RNC发送携 带组标识的释放指示消息； 接收 RNC在释放所有组内设备的 Iu接口承载及上下文， 并通 知组内设备进行 RRC连接释放后 , 反馈的释放完成消息。
连接释放单元 1202根据组标识释放组内所有设备的核心网内部承载， 具体包括： 核心网根据组标识以及建立承载时确定的组标识和承载的对应关系， 释放组内所有设 备的核心网内部 载。
本发明实施例还提供一种通信连接释放系统， 如图 13所示， 包括：
监测设备 1301 , 用于确定组内每个设备均达到通信连接释放条件； 向核心网发送携带 组标识的终止数据接收指示， 终止数据接收指示用于指示核心网发起组连接释放过程， 释 放组内设备的通信连接；
核心网 1302, 用于接收监测设备在确定组内每个设备均达到通信连接释放条件时， 发 送的携带组标识的终止数据接收指示； 发起组连接释放过程， 释放组内设备的通信连接。
对应于实施例二， 当监测设备 1301是 LTE网络中的基站时， 监测设备 1301还用于： 接收核心网根据组标识释放组内所有设备的核心网内部承载后， 发送的携带组标识的 释放指示消息； 释放所有组内设备的 S1接口承载及上下文， 并通知组内设备进行 RRC连 接释放； 向核心网反馈释放完成消息；
对应于实施例四， 当监测设备 1301是 RNC时， 监测设备 1301还用于：
接收核心网根据组标识释放组内所有设备的核心网内部承载后， 发送的携带组标识的 释放指示消息； 释放所有组内设备的 Iu接口承载及上下文， 以及通知组内设备进行 RRC 连接释放； 向核心网反馈释放完成消息；
对应于实施例四，当监测设备 1301是 UMTS网络中的基站时，监测设备 1301还用于： 接收 RNC在释放所有组内设备的 Iu接口承载及上下文后， 发送的通知释放所有组内 设备的 Iub接口承载及上下文的消息， 并释放所有组内设备的 Iub接口承载及上下文； 对应于实施例一， 当监测设备 1301是 MTC服务器或 MTC设备时， 系统中还包括： 基站， 用于接收核心网根据组标识释放组内所有设备的核心网内部承载后， 发送的携 带组标识的释放指示消息； 释放所有组内设备的 S1 接口承载及上下文， 并通知组内设备 进行 RRC连接释放； 向核心网反馈释放完成消息；
对应于实施例三， 当监测设备 1301是 MTC服务器或 MTC设备时， 系统中还包括： RNC, 用于接收核心网根据组标识释放组内所有设备的核心网内部承载后， 发送的携 带组标识的释放指示消息； 释放所有组内设备的 Iu接口承载及上下文， 以及通知组内设备 进行 RRC连接释放； 向核心网反馈释放完成消息；
此时， 核心网 1302发起组连接释放过程， 释放组内设备的通信连接， 具体包括： 根据组标识释放组内所有设备的核心网内部承载， 并向基站发送携带组标识的释放指 示消息；接收基站在释放所有组内设备的 S 1接口承载及上下文，并通知组内设备进行 RRC 连接释放后， 反馈的释放完成消息； 或者
根据组标识释放组内所有设备的核心网内部承载， 并向无线网络控制器 RNC发送携 带组标识的释放指示消息； 接收 RNC在释放所有组内设备的 Iu接口承载及上下文， 并通 知组内设备进行 RRC连接释放后 , 反馈的释放完成消息。
本发明实施例提供一种监测设备， 如图 14所示， 该装置包括：
第一处理器 1401 , 用于确定组内每个设备均达到通信连接释放条件；
第一发射器 1402 , 用于向核心网发送携带组标识的终止数据接收指示， 终止数据接收 指示用于指示核心网发起组连接释放过程， 释放组内设备的通信连接。
该装置可以为 MTC server, MTC user, eNodeB , RNC或者 NodeB。
其中， 第一处理器 1401具体用于：
确定组内每个设备完成数据交互； 或者
确定预设的定时器超时。
对应于实施例二， 当该装置为 eNodeB时， 第一处理器 1401还用于接收核心网根据组 标识释放组内所有设备的核心网内部承载后， 发送的携带组标识的释放指示消息； 释放所 有组内设备的 S 1接口承载及上下文， 并通知组内设备进行 RRC连接释放； 向核心网反馈 释放完成消息。
对应于实施例四， 当该装置为 RNC时， 第一处理器 1401还用于用于接收核心网根据 组标识释放组内所有设备的核心网内部承载后， 发送的携带组标识的释放指示消息； 释放 所有组内设备的 Iu接口承载及上下文， 以及通知组内设备进行 RRC连接释放； 向核心网 反馈释放完成消息； 或者
对应于实施例四， 当该装置为 NodeB时， 第一处理器 1401还用于用于接收 RNC在释 放所有组内设备的 Iu接口承载及上下文后，发送的通知释放所有组内设备的 Iub接口承载 及上下文的消息， 并释放所有组内设备的 Iub接口承载及上下文。
其中， 第一处理器 1401通知组内设备进行 RRC连接释放， 具体包括：
通过组广播方式向组内设备发送 RRC连接释放指示， 通知组内设备进行 RRC连接释 放。
第一处理器 1401还用于释放所有组内设备的 S 1接口承载及上下文， 具体包括： 根据组标识以及建立承载及上下文时确定的组标识和承载及上下文的对应关系， 释放 所有组内设备的 S 1接口承载及上下文； 第一处理器 1401还用于放所有组内设备的 Iu接口承载及上下文， 具体包括： 根据组标识以及建立承载及上下文时确定的组标识和承载及上下文的对应关系， 释放 所有组内设备的 Iu接口承载及上下文。
本发明实施例提供一种核心网设备装置， 如图 15所示， 该装置包括：
第二发射器 1501 , 用于接收监测设备在确定组内每个设备均达到通信连接释放条件 时， 发送的携带组标识的终止数据接收指示；
第二处理器 1502 , 用于发起组连接释放过程 , 释放组内设备的通信连接。
其中， 对应于实施例一和实施例二， 第二处理器 1502具体用于：
根据组标识释放组内所有设备的核心网内部承载， 并向基站发送携带组标识的释放指 示消息；接收基站在释放所有组内设备的 S 1接口承载及上下文，并通知组内设备进行 RRC 连接释放后， 反馈的释放完成消息； 或者
对应于实施例三和实施例四， 第二处理器 1502具体用于：
根据组标识释放组内所有设备的核心网内部承载， 并向无线网络控制器 RNC发送携 带组标识的释放指示消息； 接收 RNC在释放所有组内设备的 Iu接口承载及上下文， 并通 知组内设备进行 RRC连接释放后， 反馈的释放完成消息。
第二处理器 1502根据组标识释放组内所有设备的核心网内部承载， 具体包括： 核心网根据组标识以及建立承载时确定的组标识和承载的对应关系， 释放组内所有设 备的核心网内部承载。
本发明实施例提供一种通信连接释放方法、 装置及系统， 在组内每个设备均达到通信 连接释放条件时， 对该组设备统一进行释放， 避免了对每个设备分别进行释放， 减少了接 口信令和空口信令负荷， 提高了通信连接释放的效率。
本领域内的技术人员应明白， 本发明的实施例可提供为方法、 系统、 或计算机程序产 品。 因此， 本发明可釆用完全硬件实施例、 完全软件实施例、 或结合软件和硬件方面的实 施例的形式。 而且， 本发明可釆用在一个或多个其中包含有计算机可用程序代码的计算机 可用存储介盾 （包括但不限于磁盘存储器、 CD-ROM、 光学存储器等）上实施的计算机程 序产品的形式。
本发明是参照根据本发明实施例的方法、 设备（系统）、 和计算机程序产品的流程图 和 /或方框图来描述的。 应理解可由计算机程序指令实现流程图和 /或方框图中的每一流 程和 /或方框、 以及流程图和 /或方框图中的流程和 /或方框的结合。 可提供这些计算机 程序指令到通用计算机、 专用计算机、 嵌入式处理机或其他可编程数据处理设备的第一处 理器以产生一个机器， 使得通过计算机或其他可编程数据处理设备的第一处理器执行的指 令产生用于实现在流程图一个流程或多个流程和 /或方框图一个方框或多个方框中指定 的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方 式工作的计算机可读存储器中， 使得存储在该计算机可读存储器中的指令产生包括指令装 置的制造品， 该指令装置实现在流程图一个流程或多个流程和 /或方框图一个方框或多个 方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上， 使得在计算机 或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理， 从而在计算机或其他 可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和 /或方框图一个 方框或多个方框中指定的功能的步骤。
尽管已描述了本发明的优选实施例， 但本领域内的技术人员一旦得知了基本创造性概 念， 则可对这些实施例作出另外的变更和修改。 所以， 所附权利要求意欲解释为包括优选 实施例以及落入本发明范围的所有变更和修改。
显然， 本领域的技术人员可以对本发明进行各种改动和变型而不脱离本发明的精神和 范围。这样，倘若本发明的这些修改和变型属于本发明权利要求及其等同技术的范围之内， 则本发明也意图包含这些改动和变型在内。

Claims

权 利 要 求
1、 一种通信连接释放方法， 其特征在于， 包括：
确定组内每个设备均达到通信连接释放条件；
向核心网发送携带组标识的终止数据接收指示；
其中， 所述终止数据接收指示用于指示所述核心网发起组连接释放过程， 释放组内设 备的通信连接。
2、 如权利要求 1 所述的方法， 其特征在于， 所述确定组内每个设备均达到通信连接 释放条件， 具体包括：
确定组内每个设备完成数据交互； 或者
确定预设的定时器超时。
3、 如权利要求 1 所述的方法， 其特征在于， 向核心网发送携带组标识的终止数据接 收指示之后。 还包括：
若在长期演进 LTE网络中，所述核心网根据所述组标识释放组内所有设备的核心网内 部承载， 并向基站发送携带组标识的释放指示消息； 所述基站在接收到所述释放指示消息 后， 释放所有组内设备的 S1接口承载及上下文， 并通知组内设备进行无线资源连接 RRC 连接释放； 所述基站向所述核心网反馈释放完成消息；
若在通用移动通信系统 UMTS网络中，所述核心网根据所述组标识释放组内所有设备 的核心网内部承载，并向无线网络控制器 RNC发送携带组标识的释放指示消息；所述 RNC 在接收到所述释放指示消息后，释放所有组内设备的 Iu接口承载及上下文， 以及通知组内 设备进行 RRC连接释放； 所述 RNC向所述核心网反馈释放完成消息。
4、 如权利要求 3所述的方法， 其特征在于， 所述 RNC释放所有组内设备的 Iu接口承 载及上下文后， 还包括：
所述 RNC通知基站释放所有组内设备的 Iub接口承载及上下文。
5、 如权利要求 3所述的方法， 其特征在于， 所述通知组内设备进行 RRC连接释放， 具体包括：
通过组广播方式向组内设备发送 RRC连接释放指示， 通知组内设备进行 RRC连接释 放；
所述设备接收到所述 RRC连接释放指示后， 进行无线资源的释放过程。
6、 如权利要求 3 所述的方法， 其特征在于， 所述核心网根据所述组标识释放组内所 有设备的核心网内部承载， 具体包括：
所述核心网根据所述组标识以及建立承载时确定的组标识和承载的对应关系， 释放组 内所有设备的核心网内部承载；
所述基站释放所有组内设备的 S1接口承载及上下文， 具体包括：
所述基站根据所述组标识以及建立承载及上下文时确定的组标识和承载及上下文的 对应关系， 释放所有组内设备的 S1接口承载及上下文；
所述 RNC释放所有组内设备的 Iu接口承载及上下文， 具体包括：
所述 RNC根据所述组标识以及建立承载及上下文时确定的组标识和承载及上下文的 对应关系， 释放所有组内设备的 Iu接口承载及上下文。
7、 一种通信连接释放方法， 其特征在于， 包括：
核心网接收监测设备在确定组内每个设备均达到通信连接释放条件时， 发送的携带组 标识的终止数据接收指示；
所述核心网发起组连接释放过程， 释放组内设备的通信连接。
8、 如权利要求 7所述的方法， 其特征在于， 所述监测设备具体为：
机器类通信 MTC服务器； 或者 MTC设备； 或者无线网络控制器 RNC; 或者基站。
9、 如权利要求 7 所述的方法， 其特征在于， 所述核心网发起组连接释放过程， 释放 组内设备的通信连接， 具体包括：
在 LTE网络中， 所述核心网根据所述组标识释放组内所有设备的核心网内部承载， 并 向基站发送携带组标识的释放指示消息； 所述核心网接收所述基站在释放所有组内设备的 S1接口承载及上下文， 并通知组内设备进行无线资源连接 RRC连接释放后， 反馈的释放 完成消息；
在 UMTS网络中， 所述核心网根据所述组标识释放组内所有设备的核心网内部承载， 并向无线网络控制器 RNC发送携带组标识的释放指示消息； 所述核心网接收所述 RNC在 释放所有组内设备的 Iu接口承载及上下文， 以及通知组内设备进行 RRC连接释放后 , 反 馈的释放完成消息。
10、 如权利要求 9所述的方法， 其特征在于， 所述核心网根据所述组标识释放组内所 有设备的核心网内部承载， 具体包括：
所述核心网根据所述组标识以及建立承载时确定的组标识和承载的对应关系， 释放组 内所有设备的核心网内部承载。
11、 一种通信连接释放装置， 其特征在于， 包括：
确定单元， 用于确定组内每个设备均达到通信连接释放条件；
发送单元， 用于向核心网发送携带组标识的终止数据接收指示， 所述终止数据接收指 示用于指示所述核心网发起组连接释放过程， 释放组内设备的通信连接。
12、 如权利要求 11所述的装置， 其特征在于， 所述确定单元具体用于： 确定组内每个设备完成数据交互； 或者确定预设的定时器超时。
13、 如权利要求 11所述的装置， 其特征在于， 所述装置还包括：
第一释放单元， 用于接收所述核心网根据所述组标识释放组内所有设备的核心网内部 承载后， 发送的携带组标识的释放指示消息； 释放所有组内设备的 S 1接口承载及上下文， 并通知组内设备进行无线资源连接 RRC 连接释放； 向所述核心网反馈释放完成消息； 或 者
第二释放单元， 用于接收所述核心网根据所述组标识释放组内所有设备的核心网内部 承载后， 发送的携带组标识的释放指示消息； 释放所有组内设备的 Iu接口承载及上下文， 以及通知组内设备进行 RRC连接释放； 向所述核心网反馈释放完成消息； 或者
第三释放单元， 用于接收 RNC在释放所有组内设备的 Iu接口承载及上下文后， 发送 的通知释放所有组内设备的 iub接口承载及上下文的消息， 并释放所有组内设备的 Iub接 口承载及上下文。
14、 如权利要求 13 所述的装置， 其特征在于， 所述第一释放单元或所述第二释放单 元通知组内设备进行 RRC连接释放， 具体包括：
通过组广播方式向组内设备发送 RRC连接释放指示， 通知组内设备进行 RRC连接释 放。
15、 如权利要求 13 所述的装置， 其特征在于， 所述第一释放单元释放所有组内设备 的 S 1接口承载及上下文， 具体包括：
根据所述组标识以及建立承载及上下文时确定的组标识和承载及上下文的对应关系， 释放所有组内设备的 S 1接口承载及上下文；
所述第二释放单元释放所有组内设备的 Iu接口承载及上下文， 具体包括：
根据所述组标识以及建立承载及上下文时确定的组标识和承载及上下文的对应关系， 释放所有组内设备的 Iu接口承载及上下文。
16、 一种通信连接释放装置， 其特征在于， 包括：
指示接收单元， 用于接收监测设备在确定组内每个设备均达到通信连接释放条件时， 发送的携带组标识的终止数据接收指示；
连接释放单元， 用于发起组连接释放过程， 释放组内设备的通信连接。
17、 如权利要求 16所述的装置， 其特征在于， 所述连接释放单元具体用于： 根据所述组标识释放组内所有设备的核心网内部承载， 并向基站发送携带组标识的释 放指示消息； 接收所述基站在释放所有组内设备的 S 1 接口承载及上下文， 并通知组内设 备进行无线资源连接 RRC连接释放后 , 反馈的释放完成消息； 或者
根据所述组标识释放组内所有设备的核心网内部承载， 并向无线网络控制器 RNC发 送携带组标识的释放指示消息； 接收所述 RNC在释放所有组内设备的 Iu接口承载及上下 文， 并通知组内设备进行 RRC连接释放后， 反馈的释放完成消息。
18、 如权利要求 17 所述的装置， 其特征在于， 所述连接释放单元根据所述组标识释 放组内所有设备的核心网内部承载， 具体包括：
所述核心网根据所述组标识以及建立承载时确定的组标识和承载的对应关系， 释放组 内所有设备的核心网内部承载。
19、 一种通信连接释放系统， 其特征在于， 包括：
监测设备， 用于确定组内每个设备均达到通信连接释放条件； 向核心网发送携带组标 识的终止数据接收指示， 所述终止数据接收指示用于指示所述核心网发起组连接释放过 程， 释放组内设备的通信连接；
核心网， 用于接收监测设备在确定组内每个设备均达到通信连接释放条件时， 发送的 携带组标识的终止数据接收指示； 发起组连接释放过程 , 释放组内设备的通信连接。
20、 如权利要求 19所述的系统， 其特征在于， 所述监测设备是 LTE网络中的基站时， 所述监测设备还用于：
接收所述核心网根据所述组标识释放组内所有设备的核心网内部承载后， 发送的携带 组标识的释放指示消息； 释放所有组内设备的 S 1 接口承载及上下文， 并通知组内设备进 行无线资源连接 RRC连接释放； 向所述核心网反馈释放完成消息；
所述监测设备是 RNC时， 所述监测设备还用于：
接收所述核心网根据所述组标识释放组内所有设备的核心网内部承载后， 发送的携带 组标识的释放指示消息； 释放所有组内设备的 Iu接口承载及上下文， 以及通知组内设备进 行 RRC连接释放； 向所述核心网反馈释放完成消息；
所述监测设备是 UMTS网络中的基站时， 所述监测设备还用于：
接收 RNC在释放所有组内设备的 Iu接口承载及上下文后， 发送的通知释放所有组内 设备的 Iub接口承载及上下文的消息， 并释放所有组内设备的 Iub接口承载及上下文； 所述监测设备是 MTC服务器或 MTC设备时， 所述系统中还包括：
基站， 用于接收所述核心网根据所述组标识释放组内所有设备的核心网内部承载后， 发送的携带组标识的释放指示消息； 释放所有组内设备的 S 1 接口承载及上下文， 并通知 组内设备进行 RRC连接释放； 向所述核心网反馈释放完成消息； 或者
RNC , 用于接收所述核心网根据所述组标识释放组内所有设备的核心网内部承载后， 发送的携带组标识的释放指示消息； 释放所有组内设备的 Iu接口承载及上下文， 以及通知 组内设备进行 RRC连接释放； 向所述核心网反馈释放完成消息；
所述核心网发起组连接释放过程， 释放组内设备的通信连接， 具体包括：
根据所述组标识释放组内所有设备的核心网内部承载， 并向基站发送携带组标识的释 放指示消息； 接收所述基站在释放所有组内设备的 S1 接口承载及上下文， 并通知组内设 备进行 RRC连接释放后， 反馈的释放完成消息； 或者
根据所述组标识释放组内所有设备的核心网内部承载， 并向无线网络控制器 RNC发 送携带组标识的释放指示消息； 接收所述 RNC在释放所有组内设备的 Iu接口承载及上下 文， 并通知组内设备进行 RRC连接释放后， 反馈的释放完成消息。
PCT/CN2013/078345 2012-08-29 2013-06-28 一种通信连接释放方法、装置及系统 Ceased WO2014032469A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201210312494.8A CN103634933A (zh) 2012-08-29 2012-08-29 一种通信连接释放方法、装置及系统
CN201210312494.8 2012-08-29

Publications (1)

Publication Number Publication Date
WO2014032469A1 true WO2014032469A1 (zh) 2014-03-06

Family

ID=50182454

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2013/078345 Ceased WO2014032469A1 (zh) 2012-08-29 2013-06-28 一种通信连接释放方法、装置及系统

Country Status (2)

Country Link
CN (1) CN103634933A (zh)
WO (1) WO2014032469A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2025227962A1 (zh) * 2024-04-28 2025-11-06 华为技术有限公司 一种通信方法、通信设备、介质及程序产品

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104955171A (zh) * 2014-03-26 2015-09-30 中兴通讯股份有限公司 移动通信网络连接创建的控制方法及装置
CN105025464A (zh) * 2014-04-15 2015-11-04 中国移动通信集团公司 一种数据传输方法和设备
CN105025463A (zh) * 2014-04-15 2015-11-04 中国移动通信集团公司 一种数据传输方法和设备
CN105025589A (zh) * 2014-04-15 2015-11-04 中国移动通信集团公司 终端设备数据传输管理方法、装置、系统及相关设备
CN108617035A (zh) * 2017-01-24 2018-10-02 展讯通信（上海）有限公司 基站及其释放终端的方法
CN115550467B (zh) * 2022-08-31 2024-11-26 上海金铎禹辰水环境工程有限公司 远程终端连接方法、装置、设备及存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120004003A1 (en) * 2009-12-22 2012-01-05 Shaheen Kamel M Group-based machine to machine communication
CN102595327A (zh) * 2011-01-12 2012-07-18 中兴通讯股份有限公司 一种mbms触发方法及系统
CN102612013A (zh) * 2011-01-20 2012-07-25 华为终端有限公司 基于组的机器类型通信mtc设备的位置管理方法和设备

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120004003A1 (en) * 2009-12-22 2012-01-05 Shaheen Kamel M Group-based machine to machine communication
CN102595327A (zh) * 2011-01-12 2012-07-18 中兴通讯股份有限公司 一种mbms触发方法及系统
CN102612013A (zh) * 2011-01-20 2012-07-25 华为终端有限公司 基于组的机器类型通信mtc设备的位置管理方法和设备

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2025227962A1 (zh) * 2024-04-28 2025-11-06 华为技术有限公司 一种通信方法、通信设备、介质及程序产品

Also Published As

Publication number Publication date
CN103634933A (zh) 2014-03-12

Similar Documents

Publication Publication Date Title
EP3897000B1 (en) Methods and apparatuses for communication of terminal in mobile communication system
CN109644330B (zh) 用于通过使用切片向终端提供网络服务的方法和装置
US9723476B2 (en) Location registration for a device-to-device (D2D) user equipment
CN102149215B (zh) 传输保活信息的方法及终端和网络设备
WO2014032469A1 (zh) 一种通信连接释放方法、装置及系统
CN108370498B (zh) 传输方案的确定方法、装置和设备
KR20210006453A (ko) 재개 요청의 거부와 관련한 ue 거동
KR102476193B1 (ko) 레이트 제어 방법, 장치, 및 시스템
CN112040567A (zh) 一种恢复rrc连接的方法及装置、计算机存储介质
CN109348543A (zh) 用于机器类型通信的移动性管理实体、用户设备及方法
CN107046714B (zh) 一种数据传输方法、装置和系统
CN104349303B (zh) 设备到设备连接管理方法、装置及基站
EP3051882A1 (en) Method, apparatus and system for d2d device discovery
US20180332473A1 (en) MTC Service Management Using NFV
WO2011134427A1 (zh) 一种离线检测的方法、装置及系统
TWI489901B (zh) 實現用戶設備與外部網路之間通訊之方法及系統
CN107426785A (zh) 一种数据传输方法及装置
TW201808031A (zh) 一種網路切片選擇方法及相關設備
CN102984662A (zh) 一种基于长期演进的集群业务实现方法和集群用户终端
CN102833734A (zh) 一种传输寻呼信息的方法
WO2012003721A1 (zh) 基于网络共享资源管理的方法及系统
WO2013013571A1 (zh) 一种无线资源管理方法及其装置
CN102172090A (zh) 终端间的通信方法和设备
CN105101154B (zh) 一种设备到设备授权信息配置方法、装置及网元设备
CN104581704B (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: 13833828

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 13833828

Country of ref document: EP

Kind code of ref document: A1