WO2012079527A1 - 公共路径的建立和使用方法、m2m的通信方法及系统 - Google Patents
公共路径的建立和使用方法、m2m的通信方法及系统 Download PDFInfo
- Publication number
- WO2012079527A1 WO2012079527A1 PCT/CN2011/084073 CN2011084073W WO2012079527A1 WO 2012079527 A1 WO2012079527 A1 WO 2012079527A1 CN 2011084073 W CN2011084073 W CN 2011084073W WO 2012079527 A1 WO2012079527 A1 WO 2012079527A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- path
- base station
- public
- data
- uplink
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/30—Connection release
- H04W76/32—Release of transport tunnels
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/12—Setup of transport tunnels
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
Definitions
- the present invention claims the priority of the Chinese patent application filed on Dec. 15, 2010, the Chinese Patent Application No. 201010590124.1, the entire contents of which are incorporated herein by reference.
- the present invention relates to the field of communications, and in particular, to a method for establishing and using a public path in a wireless communication network, and a communication method and system for M2M.
- M2M machine to machine communication services will occupy an increasing proportion in the future communication technology market.
- M2M is a combination of wireless communication and information technology. It can communicate in one direction and two-way, and is used in scenarios such as security monitoring, vending machines, and goods tracking.
- the MTC (Machine Type Communications) application architecture of M2M technology mainly includes MTC Device (Machine Device), MTC Server (Machine Server), and network part (including access network element, core network element, HSS, etc.). Functional body).
- the MTC Server stores related data information of the M2M device or the group to provide the MTC service.
- the MTC Device is a hydroelectric meter reader
- the MTC Server is a hydrometer meter reading processing server, where the configuration information of the hydroelectric meter reader is stored. , and the corresponding processing of meter reading data.
- the inventors have found that at least the following problems exist in the prior art: In the process of data transmission between a large number of MTC devices and the same MTC Server, even if data transmitted between the MTC Device and the MTC Server passes the same Path, but each MTC Device still needs to establish a bearer connection and release a bearer connection with the MTC Server, and each establishing a bearer connection operation or releasing a bearer connection operation involves transferring between multiple network element devices. Signaling, therefore, will occupy more network resources and reduce the efficiency of network service processing. Summary of the invention The embodiments of the present invention provide a method for establishing and using a common path in a wireless communication network, and a communication method and system for the M2M, which can reduce occupied network resources and improve network service processing efficiency.
- a method for establishing a public path in a wireless communication network comprising: a mobility management entity sending a session establishment request message to a serving gateway;
- the session establishment response message is a response to the session establishment request message and carries network address and tunnel endpoint identifier information of the service gateway;
- a method for establishing a public path in a wireless communication network comprising: sending, by a base station, an attach request to a mobility management entity;
- the mobility management entity Receiving an initialization context request or an attach accept message sent by the mobility management entity, where the initialization context request or the attach accept message is a response to the attach request and carries a network address of the serving gateway and tunnel endpoint identifier information;
- a method for using a unidirectional uplink public path in a wireless communication network comprising:
- Radio resource control connection establishment complete message carries a public path association identifier
- a communication method of M2M including:
- the machine device of the same transmission group performs data transmission with the machine server through the public path;
- the public path is interpreted when the data transfer between the machine device of the same transfer group and the machine server ends.
- a system for establishing a public path in a wireless communication network comprising: a mobility management entity, configured to send a session establishment request message to a serving gateway; receive a session establishment response message sent by the service gateway; and send a bearer setup to the base station a request message, the bearer setup request message carries a network address of the serving gateway, and a tunnel end, identifier information; receiving a bearer setup request response sent by the base station to complete establishment of a public path; and a service gateway, configured to receive the mobile a session establishment request message sent by the management entity; sending a session establishment response message to the mobility management entity, where the session establishment response message carries network address and tunnel endpoint identifier information of the service gateway;
- a base station configured to receive a bearer setup request message sent by the mobility management entity, and send a bearer setup response message to the mobility management entity.
- a system for establishing a common path in a wireless communication network comprising: a base station, configured to send an attach request to a mobility management entity; receiving an initialization context request or an attach accept message sent by the mobility management entity; The management entity sends an initialization context response or an attach complete message to complete the establishment of the public path, where the initialization context response or attach complete message carries the network address and tunnel endpoint identifier information of the base station;
- a mobility management entity configured to receive an attach request sent by the base station; obtain a network address of the serving gateway and tunnel endpoint identifier information; send an initialization context request or an attach accept message to the base station, where the initialization context request or the attach accepting cancellation And carrying the network address and tunnel endpoint identifier information of the serving gateway; receiving an initialization context response or an attach complete message sent by the base station.
- a system for using a one-way uplink public path in a wireless communication network comprising: a device, configured to send a radio resource control connection request message to the base station; receive a radio resource control connection setup message sent by the base station; send a radio resource control connection setup complete message to the base station, where the radio resource control connection establishment complete message Carry a public path association identifier;
- a base station a radio resource control connection request message sent by the receiver device; sending a radio resource control connection setup message to the machine device; receiving a radio resource control connection setup complete message sent by the machine device; controlling according to the radio resource
- the common path associated identifier in the connection setup complete message determines a common path corresponding to the machine device; when the uplink data is sent by the receiver device, the uplink is sent to the opposite node of the common path by using the public path data.
- An M2M communication system includes:
- a network unit configured to acquire feature information of a common path corresponding to the machine device of the same transmission group; establish the public path according to the feature information; and data between the machine device and the machine server of the same transmission group At the end of the transmission, the common path is released; and the machine server is configured to perform data transmission with the machine device of the same transmission group by using a common path corresponding to the machine device of the same transmission group.
- the method for establishing and using a common path in a wireless communication network provided by the embodiment of the present invention, and the communication method and system of the M2M, by acquiring feature information of a common path corresponding to a machine device of the same transmission group, establishing a location according to the feature information
- the common path, the machine device of the co-transport group performs data transmission with the machine server through the common path, and releases the common path when the data transmission between the machine device and the machine server of the co-transport group ends. Therefore, when the MTC Device of the same group and the MTC Server perform data transmission, the public path part only involves the operation of establishing and releasing the bearer once, which reduces the signaling transmission between the nodes, thereby reducing the network resources occupied by the M2M communication.
- FIG. 1 is a schematic flowchart of a communication method of an M2M according to an embodiment of the present invention
- FIG. 2 is a schematic flowchart of a method for triggering establishment of a bidirectional public path from an eNB to an MTC Server by an MME according to an embodiment of the present invention
- FIG. 3 is a schematic flowchart of a method for triggering establishment of an uplink public path from an eNB to an MTC Server by an MME according to an embodiment of the present invention
- FIG. 4 is a schematic flowchart of a method for triggering establishment of a downlink common path from an eNB to an MTC Server by an MME according to an embodiment of the present invention
- FIG. 5 is a schematic flowchart of a method for triggering establishment of a bidirectional public path from an eNB to an MTC Server by an eNB according to an embodiment of the present invention
- FIG. 6 is a schematic flowchart of a method for triggering establishment of an uplink common path from an eNB to an MTC Server by an eNB according to an embodiment of the present disclosure
- FIG. 7 is a schematic flowchart of a method for triggering establishment of a downlink common path from an eNB to an MTC Server by an eNB according to an embodiment of the present disclosure
- FIG. 8 is a schematic flowchart of a communication method using a common path from an eNB to an MTC Server according to an embodiment of the present invention
- FIG. 9 is a schematic flowchart of a communication method using a common path from an eNB to a P-GW according to an embodiment of the present invention.
- FIG. 10 is a schematic flowchart of a method for triggering deletion of a public path from an eNB to an MTC Server by an MME according to an embodiment of the present invention
- FIG. 11 is a schematic flowchart diagram of a method for establishing a public path in a wireless communication network according to an embodiment of the present invention.
- FIG. 12 is a schematic flowchart diagram of another method for establishing a public path in a wireless communication network according to an embodiment of the present disclosure
- FIG. 13 is a schematic flowchart of a method for using a public path in a wireless communication network according to an embodiment of the present disclosure
- FIG. 14 is a schematic structural diagram of a communication system of an M2M according to an embodiment of the present invention
- FIG. 15 is a schematic structural diagram of a system for establishing a public path in a wireless communication network according to an embodiment of the present invention
- FIG. 16 is a schematic structural diagram of a system for establishing a public path in another wireless communication network according to an embodiment of the present invention
- FIG. 17 is a schematic structural diagram of a system for using a public path in a wireless communication network according to an embodiment of the present invention.
- the embodiment of the present invention provides an M2M communication method, as shown in FIG. 1 , including:
- the devices of the same transmission group have the same data transmission path, and generally have the same destination address (the same one) MTC Server) and / or QoS.
- the same data transmission path may be an eNB (evolved Node B, evolved base station) to an S-GW (Serving Gateway), and then to a P-GW (Packet Data Network Gateway), or , only the eNB to the S-GW, or the eNB to the S-GW and then to the P-GW to the MTC Server, or the S-GW to the P-GW, or the path from the S-GW to the P-GW to the MTC Server. .
- eNB evolved Node B, evolved base station
- S-GW Serving Gateway
- P-GW Packet Data Network Gateway
- the feature information of the common path includes information such as a first node and a last node of the common path and a data transmission direction of the common path.
- the common path may be established and translated by node-level signaling, or may be configured by a PVC (Permanent Virtual Circuit) (Asynchronous Transfer Mode). ) or SVC (Switched Virtual Circuit).
- the trigger for establishing and releasing may be a configuration trigger or a time trigger.
- the MTC Device group (such as a water meter) below the eNB l randomly transmits data only between 3:00-4:00 at night, then the public path may be At night, 2:59 triggers the establishment, and 3:01 triggers the translation.
- the terminal always sends data, the public path can be deleted after the establishment, and becomes a "permanent path".
- a first node and a last node of the common path and a data transmission direction of the common path may be determined according to the feature information; a tunnel is established between the first node and the last node; and, in the data
- the node of the tunnel stores the network address and interface information of the node of the node of the node; when the data transmission direction is downlink, the node of the tunnel stores the node under the node.
- the establishment of the common path may be triggered by the MME (Mobility Management Entity), or may be triggered by the eNB, or triggered by the P-GW, or may be triggered by other entities and notified to the MME and the eNB. Or the P-GW to establish a corresponding public path.
- MME Mobility Management Entity
- the common path may be a path between the eNB and the MTC Server (including the eNB of the SAE network to the S-GW and then to the P-GW to the MTC Server, or the RNC of the UMTS network to the SGSN and then to the GGSN to the MTC Server,
- the present invention takes the SAE network as an example, the UMTS network is similar, and will not be described again), the path between the eNB and the P-GW (ie, the eNB to the S-GW and then to the P-GW), and between the S-GW and the P-GW. Path, etc.
- the public path may be an up path, a down path, or a bidirectional path. In the following, the process of establishing a public path will be described in further detail in combination with the above different situations.
- a method for triggering establishment of a bidirectional public path from an eNB to an MTC Server by the MME includes:
- the MME needs to establish a bidirectional public path for a group of MTC devices by using a configuration trigger or a time trigger or other trigger, and send a session establishment request (Create Session Request) message to the S-GW.
- a session establishment request Create Session Request
- the S-GW sends a session establishment request message to the P-GW, where the session establishment request message carries an S-GW IP address and a TEID (Train Endpoint Identifier) information.
- the P-GW receives the session establishment request. After the message, the IP address and TEID information of the S-GW are recorded, thereby establishing a downlink path of the P-GW to the S-GW.
- the IP address may be carried in the GTP message parameter of the delivery, or may be carried in the source address of the sent IP packet.
- the session establishment request message may further carry an information indication, which is used to indicate whether the P-GW needs to return the IP address or TEID information of the P-GW.
- the established tunnel may be an IP in IP tunnel, or a GRE (Generic Routing Encapsulation) tunnel, or an IPSEC (Internet Protocol Security) tunnel.
- GRE Generic Routing Encapsulation
- IPSEC Internet Protocol Security
- the P-GW sends a session establishment response (Create Session Response) message to the S-GW, where the session establishment response message carries the IP address and TEID information of the P-GW.
- the S-GW After receiving the session establishment response message, the S-GW records the P. - The IP address and TEID information of the GW, thereby establishing an uplink path of the S-GW to the P-GW.
- the S-GW sends a session establishment response message to the MME, where the session establishment response message carries the IP address and the TEID information of the S-GW.
- the MME obtains the S- from the received session establishment response message. GW's IP address and TEID information.
- the MME sends a bearer setup request message to the eNB, where the bearer setup request message carries the IP address and TEID information of the S-GW.
- the eNB After receiving the bearer setup request message, the eNB records the IP address and TEID information of the S-GW. An uplink path from the eNB to the S-GW is established.
- the eNB sends a bearer setup response message to the MME, where the bearer setup response message carries the IP address and TEID information of the eNB.
- the MME obtains the IP address and TEID of the eNB from the bearer setup response message. information.
- the MME sends a bearer modification request message to the S-GW, where the bearer modification request message carries an IP address and TEID information of the eNB.
- the S-GW After receiving the bearer modification request message, the S-GW records the IP address and the TEID information of the eNB. This establishes the downlink path of the S-GW to the eNB.
- the S-GW sends a bearer modification response message to the MME.
- the common path to be established is a partial path in the bidirectional path between the eNB and the MTC Server, it may be implemented by appropriately omitting some steps in the embodiment described in FIG. 2.
- the common path to be established is a bidirectional path from the eNB to the P-GW
- the common path can be established by omitting step 203 in the embodiment depicted in FIG.
- the common path to be established is a bidirectional path from the eNB to the S-GW
- the common path can be established by omitting steps 202-204 in the embodiment depicted in FIG.
- the common path to be established is a bidirectional path from the S-GW to the P-GW, the common path can be established by omitting steps 203, 206-209 in the embodiment depicted in FIG. Other embodiments are similar and will not be described again.
- a method for triggering an uplink public path from an eNB to an MTC Server is triggered by an MME, including:
- the MME needs to establish an uplink common path for a group of MTC devices by using a configuration trigger or a time trigger or other trigger, and send a session establishment request message to the S-GW.
- the S-GW sends a session establishment request message to the P-GW.
- the session establishment request message may further carry an information indication, where the information indication is used to indicate whether the P-GW needs to return the IP address or TEID information of the P-GW.
- the established tunnel may be an IP in IP tunnel, or a GRE (Generic Routing Encapsulation Protocol) tunnel, or an IPSEC tunnel.
- GRE Generic Routing Encapsulation Protocol
- IPSEC IPSEC tunnel
- the P-GW sends a session establishment response message to the S-GW, where the session establishment response message carries the IP address and TEID information of the P-GW.
- the S-GW After receiving the session establishment response message, the S-GW records the IP address of the P-GW. And the TEID information, thereby establishing an uplink path of the S-GW to the P-GW.
- the S-GW sends a session establishment response message to the MME, where the session establishment response message carries the IP address and the TEID information of the S-GW.
- the MME obtains the S- from the received session establishment response message. GW's IP address and TEID information.
- the MME sends a bearer setup request message to the eNB, where the bearer setup request message carries the IP address and TEID information of the S-GW. After receiving the bearer setup request message, the eNB records the IP address and TEID information of the S-GW. An uplink path from the eNB to the S-GW is established.
- the bearer setup request message may further carry an information indication, where the information indication is used to indicate that the eNB does not need to return the IP address or TEID information of the eNB to the S-GW.
- the eNB sends a bearer setup response message to the MME.
- the common path to be established is a partial path in the uplink path between the eNB and the MTC Server, it may be implemented by appropriately omitting some steps in the embodiment described in FIG.
- the public path to be established is the uplink path of the eNB to the P-GW
- the common path can be established by omitting step 303 in the embodiment described in FIG.
- a method for triggering establishment of a downlink common path from an eNB to an MTC Server by an MME includes: 401.
- the MME determines that a downlink common path needs to be established for a group of MTC devices by using a configuration trigger or a time trigger or other trigger, and sends a session establishment request message to the S-GW.
- the S-GW sends a session establishment request message to the P-GW, where the session establishment request message carries the IP address and TEID information of the S-GW.
- the P-GW After receiving the session establishment request message, the P-GW records the IP address of the S-GW. And TEID information, thus establishing a downlink path from the P-GW to the S-GW.
- the IP address may be carried in the GTP message parameter of the delivery, or may be carried in the source address of the sent IP packet.
- the session establishment request message may further carry an information indication, which is used to indicate that the P-GW does not need to return the IP address or TEID information of the P-GW.
- the established tunnel may be an IP in IP tunnel, or a GRE tunnel, or an IPSEC tunnel.
- the specific method for establishing a tunnel can refer to the prior art, and details are not described herein again.
- the P-GW sends a session establishment response message to the S-GW.
- the S-GW sends a session setup response message to the MME, where the session setup response message may carry an information indication, where the information indication is used to indicate that the eNB needs to return the IP address or TEID information of the P-GW.
- the MME sends a bearer setup request message to the eNB, where the bearer setup request message carries an information indication, where the information indication is used to indicate that the eNB needs to return the IP address or TEID information of the P-GW.
- the eNB sends a bearer setup response message to the MME, where the bearer setup response message carries the IP address and TEID information of the eNB.
- the MME obtains the IP address and TEID information of the eNB from the bearer setup response message. .
- the MME sends a bearer modification request message to the S-GW, where the bearer modification request message carries an IP address and TEID information of the eNB.
- the S-GW After receiving the bearer modification request message, the S-GW records the IP address and TEID information of the eNB. This establishes the downlink path of the S-GW to the eNB.
- the S-GW sends a bearer modification response message to the MME.
- the common path to be established is a partial path in the downlink path between the eNB and the MTC Server, it may be implemented by appropriately omitting some steps in the embodiment described in FIG.
- the common path to be established is the downlink path of the eNB to the P-GW
- the common path can be established by omitting step 403 in the embodiment described in FIG.
- a method for triggering establishment of a bidirectional public path from an eNB to an MTC Server by an eNB includes:
- the eNB determines that a bidirectional public path needs to be established for a group of MTC devices by using a configuration trigger or a time trigger or other trigger.
- the eNB may simulate a UE, and similarly, the UE sends an attach request to the MME, just like the UE has accessed the eNB;
- the MME After receiving the attach request, the MME sends a session establishment request message to the S-GW.
- the S-GW After receiving the session establishment request message, the S-GW sends a session establishment request message to the P-GW, where the session establishment request message carries the IP address and TEID information of the S-GW.
- the P-GW After receiving the session establishment request message, the P-GW receives the session establishment request message. The IP address and TEID information of the S-GW are recorded, thereby establishing a downlink path of the P-GW to the S-GW.
- the IP address may be carried in the GTP message parameter of the delivery, or may be carried in the source address of the sent IP packet.
- the session establishment request message may further carry an information indication, which is used to indicate whether the P-GW needs to return the IP address or TEID information of the P-GW.
- the established tunnel may be an IP in IP tunnel, or a GRE tunnel, or an IPSEC tunnel.
- the specific method for establishing a tunnel can refer to the prior art, and details are not described herein again.
- the P-GW sends a session establishment response message to the S-GW, where the session establishment response message carries the IP address and TEID information of the P-GW.
- the S-GW After receiving the session establishment response message, the S-GW records the IP address of the P-GW. And the TEID information, thereby establishing an uplink path of the S-GW to the P-GW.
- the S-GW sends a session establishment response message to the MME, where the session establishment response message carries the IP address and TEID information of the S-GW.
- the MME obtains the S- from the received session establishment response message. GW's IP address and TEID information.
- the MME sends an Initial Context Setup Request/Attach Accept message to the eNB, where the Initialization Context Request/Admission Accept message carries the IP address and TEID information of the S-GW.
- the eNB receives the Initialization Context Request/ After the attach accept message, the IP address and TEID information of the S-GW are recorded, thereby establishing an uplink path of the eNB to the S-GW.
- the eNB sends an Initial Context Setup Response/Attach Complete message to the MME, where the initialization context response/attach is completed.
- the message carries the IP address and TEID information of the eNB.
- the MME obtains the IP address and TEID information of the eNB from the initialization context response/attach complete message.
- the MME sends a bearer modification request message to the S-GW, where the bearer modification request message carries an IP address and TEID information of the eNB.
- the S-GW After receiving the bearer modification request message, the S-GW records the IP address and TEID information of the eNB. This establishes the downlink path of the S-GW to the eNB.
- the S-GW sends a bearer modification response message to the MME.
- the common path to be established is a partial bidirectional path in the path between the eNB and the MTC Server, it can be implemented by appropriately omitting some steps in the embodiment described in FIG.
- the common path to be established is a bidirectional path from the eNB to the P-GW
- the common path can be established by omitting step 504 in the embodiment depicted in FIG.
- the common path to be established is a bidirectional path from the eNB to the S-GW
- the common path can be established by omitting steps 503-505 in the embodiment depicted in FIG.
- the common path to be established is a bidirectional path from the S-GW to the P-GW
- the common path can be established by omitting steps 504, 507-510 in the embodiment depicted in FIG.
- a method for triggering an uplink common path from an eNB to an MTC Server is triggered by an eNB, including:
- the eNB determines that an uplink public path needs to be established for a group of MTC devices by using a configuration trigger or a time trigger or other trigger, and sends an attach request to the MME.
- the MME After receiving the attach request, the MME sends a session establishment request message to the S-GW.
- the S-GW After receiving the session establishment request message, the S-GW sends a session establishment request message to the P-GW.
- the session establishment request message may further carry an information indication, where the information indication is used to indicate whether the P-GW needs to return the IP address or TEID information of the P-GW.
- the established tunnel may be an IP in IP tunnel, or a GRE tunnel, or an IPSEC tunnel.
- the specific method for establishing a tunnel can refer to the prior art, and details are not described herein again.
- the P-GW sends a session establishment response message to the S-GW, where the session establishment response message carries the IP address and TEID information of the P-GW. After receiving the session establishment response message, the S-GW records the IP address of the P-GW. And the TEID information, thereby establishing an uplink path of the S-GW to the P-GW. 606.
- the S-GW sends a session establishment response message to the MME, where the session establishment response message carries the IP address and the TEID information of the S-GW. After receiving the session establishment response message, the MME obtains the S- from the received session establishment response message. GW's IP address and TEID information.
- the MME sends an initialization context request/attach accept message to the eNB, where the initialization context request/attach accept message carries the IP address and TEID information of the S-GW.
- the eNB After receiving the initialization context request/attach accept message, the eNB records the S-GW. The IP address and TEID information, thus establishing the uplink path of the eNB to the S-GW.
- the eNB sends an initialization context response/attach complete message to the MME.
- the common path to be established is a partial path in the uplink path between the eNB and the MTC Server, it can be implemented by appropriately omitting some steps in the embodiment described in FIG.
- the public path to be established is the uplink path of the eNB to the P-GW
- the common path can be established by omitting step 604 in the embodiment depicted in FIG.
- a method for triggering a downlink common path from an eNB to an MTC Server is triggered by an eNB, including:
- the eNB determines that a downlink common path needs to be established for a group of MTC devices by using a configuration trigger or a time trigger or other trigger, and sends an attach request to the MME.
- the MME After receiving the attach request, the MME sends a session establishment request message to the S-GW.
- the S-GW After receiving the session establishment request message, the S-GW sends a session establishment request message to the P-GW, where the session establishment request message carries the IP address and TEID information of the S-GW.
- the P-GW After receiving the session establishment request message, the P-GW receives the session establishment request message. The IP address and TEID information of the S-GW are recorded, thereby establishing a downlink path of the P-GW to the S-GW.
- the IP address may be carried in the GTP message parameter of the delivery, or may be carried in the source address of the sent IP packet.
- the session establishment request message may further carry an information indication, which is used to indicate that the P-GW does not need to return the IP address or TEID information of the P-GW.
- the established tunnel may be an IP in IP tunnel, or a GRE tunnel, or an IPSEC tunnel.
- the specific method for establishing a tunnel can refer to the prior art, and details are not described herein again.
- the P-GW sends a session establishment response message to the S-GW.
- the S-GW sends a session setup response message to the MME, where the session setup response message carries an information indication, where the information indication is used to indicate that the eNB needs to return to the P-GW. IP address or TEID information.
- the MME sends an initialization context request/attach accept message to the eNB, where the initialization context request/attach accept message carries an information indication, where the information indicates an IP address or TEID information used to indicate that the eNB needs to return to the P-GW.
- the eNB sends an initialization context response/attach complete message to the MME, where the initialization context response/attach complete message carries the IP address and TEID information of the eNB.
- the MME receives the initialization context response/ The IP address and TEID information of the eNB are obtained in the attach complete message.
- the MME sends a bearer modification request message to the S-GW, where the bearer modification request message carries an IP address and TEID information of the eNB.
- the S-GW After receiving the bearer modification request message, the S-GW records the IP address and TEID information of the eNB. This establishes the downlink path of the S-GW to the eNB.
- the S-GW sends a bearer modification response message to the MME.
- the common path to be established is a partial path in the downlink path between the eNB and the MTC Server, it can be implemented by appropriately omitting some steps in the embodiment described in FIG.
- the public path to be established is the downlink path of the eNB to the P-GW
- the common path can be established by omitting step 704 in the embodiment described in FIG.
- the machine device of the same transmission group performs data transmission with the machine server by using the public path;
- a radio bearer is established for the equipment of the same transmission group; when the public path is an uplink path or a bidirectional path, the established radio bearer is set in the base station. Corresponding relationship with the public path; and when the device of the same transmission group sends the uplink data through the established radio bearer, the base station determines the corresponding public path according to the corresponding relationship between the set radio bearer and the public path, and the The uplink data is sent to the machine server through the determined public path.
- the base station When the common path is a downlink path or a bidirectional path, the base station sets a correspondence between the established radio bearer and the public path, and sets a correspondence between the device information or the network address and the radio bearer;
- the base station determines the correspondence between the device information in the downlink data and the set device information and the radio bearer, or according to the network address in the downlink data and the set device Corresponding relationship between the network address and the radio bearer determines a corresponding radio bearer; the base station sends the downlink data to the corresponding machine device by using the determined radio bearer.
- a bearer establishes a filter that sets attributes of different machine devices, such as an IP address and/or a device identifier and/or a communication port, and a set of attributes corresponds to a radio bearer.
- the base station determines, by the filter, which non-present bearer the downlink data is sent to.
- the MTC Device needs to obtain the IP address of the MTC Device before the MTC Device sends the data.
- the IP address can be obtained when the data is attached, or can be allocated to the network before the data is sent.
- the public path of the eNB-MTC server is established, the MTC Device may not be assigned an IP address.
- the MTC Server receives the data of each MTC Device from the same path, and only uses the application identifier or device identifier included in the data. To distinguish between different MTC Devices.
- the common path of the eNB to the MTC Server and the eNB to the P-GW is taken as an example to further describe the communication method using the public path in further detail.
- a communication method using a common path from an eNB to an MTC Server includes:
- the MTC Device sends a RRC Connection Request message to the eNB.
- the eNB After receiving the radio resource control connection request message, the eNB sends a radio resource control connection setup (RRC Connection Setup) message to the MTC Device.
- RRC Connection Setup radio resource control connection setup
- the MTC Device After receiving the RRC connection establishment setup message, the MTC Device sends a RRC Connection Setup Complete message to the eNB, where the RRC connection establishment complete message carries the public path association identifier.
- the public path association identifier includes a group ID or a device ID or a public path ID.
- the NAS message may also be carried in the RRC connection request message.
- the eNB may not transmit the NAS to the MME, or even perform any interaction with the MME, or only perform an interactive security authentication operation. It is not necessary for the MME to perform a bearer setup operation.
- the public path association identifier may not be carried in the RRC connection establishment complete message, but the public path association identifier may be carried in the RRC connection request message.
- the eNB sends a radio bearer setup (RB Establish) message to the MTC Device.
- RB Establish radio bearer setup
- the eNB associates the MTC Device with the public path according to the public path association identifier.
- the eNB may associate the identifier according to the public path with the MTC Device.
- the established RB Radio Bearer
- the public path is the downlink path, that is, the MTC Device only downloads data from the MTC Server
- the eNB may associate the public path with the RB established by the MTC Device with the common path corresponding to the MTC Device, and associate the device ID with the MTC Device.
- the established RB corresponds.
- the eNB may associate the RB established for the MTC Device with the common path corresponding to the MTC Device according to the common path association identifier, and The device ID corresponds to the RB established for the MTC Device.
- the MTC Device sends the uplink data by using the RB, and after receiving the uplink data, the eNB transmits the uplink data to the MTC Server by using a corresponding public path.
- the public path is the path from the eNB to the MTC Server.
- the IP address of the MTC Device may not be obtained.
- the MTC Server After the MTC Server receives the data of each MTC Device from the same path, the MTC Server only includes the data.
- the application ID or device ID can distinguish different MTC devices. Therefore, the uplink data may be original data without an IP header, or may be data with an IP header added.
- the eNB establishes respective RBs for these MTC devices.
- the MTC device uploads data through the RB
- the eNB receives data through the RB.
- upload the received data to the MTC Server through the corresponding public path.
- the MTC Server can also distinguish which MTC Device the data comes from based on the device ID or the application layer identifier in the data.
- the MTC Server sends the downlink data by using the corresponding common path. After receiving the downlink data, the eNB determines the corresponding RB according to the device ID in the downlink data, and transmits the downlink data to the corresponding MTC Device by using the RB.
- the downlink data may be original data without an IP header, or may be data with an IP header added.
- the eNB determines the corresponding RB according to the device ID carried in the received data, and sends the data to the MTC Device through the RB.
- the MTC Device may not carry any NAS message, or the eNB may directly establish an RB after receiving the RRC connection request message.
- a communication method using a common path from an eNB to a P-GW includes:
- the MTC Device sends a radio resource control connection request message to the eNB, where the radio resource control connection request message carries a public path association identifier.
- the public path association identifier includes a group ID or a device ID or a public path ID.
- the P-GW is external to the MTC Server, and therefore, the data sent by the MTC Device must have an IP header when the P-GW is sent out.
- the eNB sends a radio bearer setup message to the MTC Device.
- the eNB associates the MTC Device with the public path according to the public path association identifier.
- the eNB may associate the RB established by the MTC Device with the public path corresponding to the MTC Device.
- the common path is the downlink path, that is, when the MTC device downloads data from the MTC server
- the eNB may associate the RB established for the MTC Device with the common path corresponding to the MTC Device according to the common path association identifier, and associate the device ID with the MTC Device.
- the established RB corresponds.
- the eNB may associate the public path with the RB established by the MTC Device corresponding to the common path corresponding to the MTC Device, and The device ID or the IP address information of the MTC Device corresponds to the RB established for the MTC Device.
- the MTC Device sends the uplink data by using the RB. After receiving the uplink data, the eNB transmits the uplink data to the P-GW through the corresponding public path, and the P-GW transmits the uplink data to the MTC Server.
- the MTC Device IP address cannot be obtained only when the public path is the path from the eNB to the MTC Server. This is because the MTC Server only receives the data of each MTC Device from the same path.
- the application identifier or the device identifier can be used to distinguish the different MTC devices.
- the public path is the path from the eNB to the P-GW.
- the IP address of the MTC Device needs to be obtained, and the uplink data is added and sent in the uplink data.
- the IP address of the MTC Device may be acquired at the time of attachment, or may be allocated to the access network before the data is sent.
- the eNB may assign each MTC Device when the MTC Device is accessed. Match the same or different IP address.
- Each MTC device sends data carrying the IP address assigned to the eNB to the eNB through the RB.
- the eNB After receiving the uplink data, the eNB transmits the uplink data to the P-GW through the corresponding public path, and the P-GW uses the IP in the uplink data.
- the address sends the uplink data to the corresponding MTC Server.
- the eNB does not allocate an IP address to the MTC Device, but adds an IP header to the uplink data when the MTC Device sends the original uplink data through the RB, and the destination address is the MTC Server.
- the eNB transmits the uplink data through the corresponding public path.
- the P-GW sends the uplink data to the corresponding MTC Server according to the destination address in the uplink data.
- the eNB does not allocate an IP address to the MTC Device.
- the MTC Device sends the original uplink data through the RB
- the eNB transmits the uplink data to the P-GW through the corresponding public path, and the P-GW receives the uplink data and then uplinks the uplink data.
- An IP header is added to the data, and the uplink data to which the IP header is added is sent to the corresponding MTC Server.
- the MTC Server sends the downlink data, and after receiving the downlink data, the P-GW transmits the downlink data to the eNB by using a corresponding common path. After receiving the downlink data, the eNB determines, according to the IP address or the device ID in the downlink data. RB, and transmit the downlink data to the corresponding MTC Device through the RB
- the eNB may allocate different IP addresses for each MTC Device when accessing.
- the eNB sets the IP quintuple information (ie, the source IP address, the destination IP address, the source port number, the destination port number, the protocol name, and the like) of the MTC Device and the RB, and the P-GW sets the IP address segment of the MTC Device.
- the MTC Server sends the downlink data carrying the IP address information.
- the P-GW determines the corresponding public path according to the IP address information in the downlink data, and transmits the downlink data to the eNB through the public path, and the eNB receives the downlink data.
- the corresponding RB is determined according to the IP address information in the downlink data, and the downlink data is transmitted to the corresponding MTC Device by using the RB.
- an eNB has 1000 group devices sharing a common path. They will concentrate on sending data at 3: 00-4: 00 in the morning, but will not access these devices at the same time, but will randomly pick up random connections. Into these devices, each device is connected for 5 minutes for data transfer, and will not be connected to the device after the transfer is completed.
- the eNB reserves 150 IP addresses for the group of devices. Each access device allocates an IP address when accessing the device. After the access is complete, the IP address is released. After the other devices are accessed, the released IP addresses are assigned to these devices. Equipment.
- the P-GW After the public path is established at 2:59 am, the P-GW records the correspondence between the 150 IP addresses and the public path.
- the eNB allocates an IP address to the MTC Device, the RB corresponding to the MTC Device is used. The IP address corresponds.
- the MTC Device sends uplink data (the source address of the data is the IP address assigned to it, the source port is the port number assigned by the MTC Device, the destination address is the IP address of the MTC Server, and the destination port is the port of the MTC Sever).
- the MTC Server In response to the MTC Device, the MTC Server will reply with a data.
- the destination address in the IP header of the reply data is the IP address of the MTC Device
- the destination port is the port of the MTC Device
- the P-GW receives the data of the reply.
- the eNB determines an RB corresponding to the MTC Device according to information such as a destination address (ie, an IP address of the MTC Device) and a destination port, and sends the data to the MTC Device through the RB.
- the eNB may assign the same IP address to each MTC Device, and each MTC Device sends the IP address related data information to the eNB.
- the eNB sets the correspondence between the ID of the MTC Device and the RB, and the P-GW sets the correspondence between the IP address of the MTC Device and the public path.
- the MTC Server sends the downlink data that carries the IP address assigned to the MTC Device.
- the P-GW determines the public path according to the IP address of the MTC Device in the downlink data, and transmits the downlink data to the eNB through the public path. .
- the eNB determines a corresponding RB according to the device ID in the downlink data, and transmits the downlink data to the corresponding MTC Device by using the RB.
- the MTC Server sends the downlink data carrying a specific IP address, and after receiving the downlink data, the P-GW determines the public path according to the IP address in the downlink data, and transmits the downlink data to the eNB through the public path. After receiving the downlink data, the eNB determines a corresponding RB according to the device ID in the downlink data, and transmits the downlink data to the corresponding MTC Device by using the RB.
- the MTC Device does not send an RRC connection request to establish a signaling connection and an RB data connection, but directly transmits data to the eNB at a certain time-frequency resource, and the eNB
- the identification information (such as the group ID) in the received data determines the associated public path through which the data is sent to the MTC. Server or P-GW.
- the eNB After receiving the data from the MTC Server or the P-GW through the public path, the eNB directly sends the data to the corresponding MTC Device according to the identifier information or the IP address in the data.
- a method for deleting a public path from an eNB to an MTC Server by using an MME includes:
- the MME determines that a public path established for a group of MTC devices needs to be deleted due to configuration trigger or time trigger or other trigger, and sends a session deletion request to the S-GW.
- the S-GW sends a session deletion request message to the P-GW.
- the P-GW sends a session deletion response (Delete Session Response) message to the S-GW.
- Delete Session Response Delete Session Response
- the S-GW sends a session deletion response message to the MME.
- the MME sends a Release Bearer Request message to the eNB.
- the eNB sends a Release Bearer Response message to the MME.
- the established common path is a partial path in the path between the eNB and the MTC Server, it can be realized by appropriately omitting some steps in the embodiment described in FIG.
- the common path can be translated by omitting step 1003 in the embodiment depicted in FIG.
- the common path can be released by omitting steps 1002-1004 in the embodiment depicted in FIG.
- the common path can be released by omitting steps 1003, 1006-1007 in the embodiment depicted in FIG.
- the eNB may perform a bearer deletion procedure or a Detach (Detach) procedure of a normal UE to delete the public path.
- a bearer deletion procedure or a Detach (Detach) procedure of a normal UE to delete the public path.
- the M2M communication method provided by the embodiment of the present invention is obtained by acquiring the same path transmission group And the characteristic information of the common path corresponding to the machine device, the public path is established according to the feature information, and the machine device of the same transmission group performs data transmission with the machine server through the common path, and the machine equipment of the same transmission group The public path is released at the end of the data transfer between the machine servers. Therefore, when the MTC Device of the same group and the MTC Server perform data transmission, the public path part only involves the operation of establishing a bearer and releasing the bearer once, which reduces the signaling transmission between the nodes, thereby reducing the network resources occupied by the M2M communication. Improve the processing efficiency of M2M network services.
- the embodiment of the present invention further provides a method for establishing a common path in a wireless communication network, as shown in FIG.
- the mobility management entity sends a session establishment request message to the serving gateway.
- the mobility management entity sends a session establishment request message to the serving gateway when the public path establishment trigger condition is met, where the public path establishment trigger condition includes a preset configuration condition, a preset startup time, or a network management/ Maintain the operation instructions issued by the system.
- the public path establishment trigger condition includes a preset configuration condition, a preset startup time, or a network management/ Maintain the operation instructions issued by the system.
- the established common path includes a path between the base station-serving gateway, a path between the base station-serving gateway-packet data network gateway, or a base station-serving gateway-packet data network gateway-machine server path.
- the established public path is a one-way upstream path or a two-way path.
- the mobile management entity receives the session establishment response message sent by the service gateway, where the session establishment response message is a response to the session establishment request message and carries the network address and tunnel endpoint identifier information of the service gateway;
- the established common path is a bidirectional path between the eNB and the S-GW to the P-GW to the MTC Server.
- the S-GW After receiving the session establishment request message sent by the MME, the S-GW sends a session establishment to the P-GW.
- a request message the session establishment request message carrying an IP address and TEID information of the S-GW.
- the P-GW After receiving the session establishment request message sent by the S-GW, the P-GW records the IP address and TEID information of the S-GW in the session establishment request message.
- a tunnel is established between the P-GW and the MTC Server.
- the P-GW sends a session establishment response message to the S-GW, where the session establishment response message carries the IP address and TEID information of the P-GW.
- the S-GW After receiving the session establishment response message sent by the P-GW, the S-GW records the IP address and TEID information of the P-GW in the session establishment response message.
- the S-GW sends a session establishment response message to the MME, where the session establishment response message carries the IP address and TEID information of the S-GW.
- the mobility management entity sends a bearer setup request message to the base station, where the bearer is established.
- the request message carries network address and tunnel endpoint identifier information of the serving gateway;
- the mobility management entity receives the bearer setup request response sent by the base station to complete the establishment of the public path.
- the path of the MME to the eNB is taken as an example.
- the MME After receiving the bearer setup response message sent by the eNB, the MME sends a bearer modification request message to the S-GW, where the IP address and TEID of the tamper request message eNB are sent. information.
- the S-GW After receiving the modification request message, the S-GW records the IP address and TEID information of the eNB, and sends a bearer modification response message to the MME.
- the mobile management entity sends a session establishment request message to the service gateway, and receives the network address and tunnel endpoint identifier information that is sent by the service gateway and carries the service gateway.
- the session establishment response message sends a bearer setup request message carrying the network address of the serving gateway and the tunnel endpoint identifier information to the base station, and receives the establishment of the bearer establishment request response complete public path sent by the base station. Therefore, when the same group of MTC Device and the MTC Server perform data transmission, the common path part only involves the operation of establishing the bearer once, which reduces the signaling transmission between the nodes, thereby reducing the network resources occupied by the M2M communication and improving the M2M. The processing efficiency of network services.
- the embodiment of the present invention further provides a method for establishing a public path in a wireless communication network, as shown in FIG. 12, including:
- the base station sends an attach request to the mobility management entity.
- the base station sends an attach request to the mobility management entity when the triggering condition is established.
- the common path establishment triggering condition includes a preset configuration condition, a preset startup time, or a network management/maintenance system. Operation instructions.
- the established common path includes a path between the base station-serving gateway, a path between the base station-serving gateway-packet data network gateway, or a base station-serving gateway-packet data network gateway-machine server path.
- the established public path is a one-way upstream path or a two-way path.
- the base station receives an initialization context request or an attach accept message sent by the mobility management entity, where the initialization context request or the attach accept message is a response to the attach request and carries a network address of the serving gateway and tunnel endpoint identifier information;
- the established common path is a bidirectional path between the eNB and the S-GW to the P-GW to the MTC Server.
- the MME sends a session to the S-GW.
- Set up a request message After receiving the session establishment request message, the S-GW sends a session establishment request message to the P-GW, where the session establishment request message carries the IP address and TEID information of the S-GW.
- the P-GW After receiving the session establishment request message, the P-GW records the IP address and TEID information of the S-GW, establishes a tunnel between the P-GW and the MTC Server, and the P-GW sends a session establishment response message to the S-GW, where the session is established.
- the response message carries the IP address and TEID information of the P-GW.
- the S-GW After receiving the session establishment response message, the S-GW records the IP address and TEID information of the P-GW, and sends a session establishment response message to the MME, where the session establishment response message carries the IP address and TEID information of the S-GW.
- the MME After receiving the session setup response message, the MME sends an initialization context request or an attach accept message to the eNB, where the initialization context request or the attach accept message carries the IP address and TEID information of the S-GW.
- the base station sends an initialization context response or an attach complete message to the mobility management entity to complete establishment of a common path, where the initialization context response or attach complete message carries the network address and tunnel endpoint identifier information of the base station.
- the MME After receiving the initialization context response or the attach complete message, the MME sends a bearer modification request message to the S-GW, where the bearer modification request message carries the IP address and TEID information of the eNB.
- the S-GW After receiving the bearer modification request message, the S-GW records the IP address and TEID information of the eNB, and the S-GW sends a tampering response message to the MME.
- the base station sends an attach request to the mobility management entity, and receives the network address and the tunnel end of the service gateway sent by the mobility management entity, and the identifier, An initialization context request or an attach accept message is sent, and an initialization context response or an attach complete message carrying the network address and tunnel endpoint identifier information of the base station is sent to the mobility management entity to complete establishment of the public path. Therefore, when the same group of MTC Device and the MTC Server perform data transmission, the public path part only involves the operation of establishing the bearer once, which reduces the signaling transmission between the nodes, thereby reducing the network resources occupied by the M2M communication and improving the M2M. The processing efficiency of network services.
- the embodiment of the present invention further provides a method for using a one-way uplink public path in a wireless communication network, as shown in FIG.
- the common path used is a unidirectional uplink common path, including an uplink path between the base station and the serving gateway, and the base station-serving gateway-packet data Uplink path between network gateways, or between base station-service gateway-packet data network gateway-machine server
- the public path is a bidirectional public path, including a bidirectional path between the base station and the serving gateway, a bidirectional path between the base station and the serving gateway and the packet data network gateway, or a base station-serving gateway-packet data network gateway - A two-way path between machine servers.
- the base station sends a radio resource control connection establishment message to the device.
- the base station receives a radio resource control connection establishment completion message sent by the device, where the radio resource control connection establishment completion message carries a public path association identifier.
- the base station determines, according to the public path associated identifier, a public path corresponding to the machine device.
- the base station may determine a one-way uplink public path corresponding to the machine device according to the common path associated identifier.
- the base station may determine the bidirectional public path corresponding to the machine device according to the common path associated identifier.
- the uplink data is sent to the opposite node of the common path by using the common path.
- the base station may send the uplink data to the opposite node of the one-way uplink public path through the one-way uplink common path when the uplink data is sent by the receiver device.
- the base station may also send the uplink data to the opposite node of the bidirectional public path through the bidirectional public path when the uplink data is sent by the receiver device.
- the base station may further determine, according to the device identifier in the downlink data, the corresponding device device when receiving the downlink data from the opposite end node of the bidirectional public path by using the bidirectional public path, and send the foregoing to the determined device device. Downstream data.
- the method for using the common path in the wireless communication network sends a radio resource control connection setup message to the device by using a radio resource control connection request message sent by the base station receiver device, and receives the bearer sent by the device a radio resource control connection establishment complete message of the public path association identifier, determining a common path corresponding to the machine device according to the common path associated identifier, and using the public path to the public path when the uplink data is sent by the receiver device
- the opposite node of the public path sends the uplink data. .
- the public path part only involves the operation of establishing the bearer once, which reduces the signaling transmission between the nodes, thereby reducing the network resources occupied by the M2M communication and improving the M2M.
- the processing efficiency of network services is only involves the operation of establishing the bearer once, which reduces the signaling transmission between the nodes, thereby reducing the network resources occupied by the M2M communication and improving the M2M.
- the embodiment of the present invention further provides an M2M communication system, as shown in FIG. 14, including:
- the network unit 1401 is configured to acquire feature information of a common path corresponding to the machine device of the same transmission group; establish the common path according to the feature information; between the machine device of the same transmission group and the machine server 1402 At the end of the data transmission, release the public path;
- the machine server 1402 is configured to perform data transmission with the machine device of the same transmission group by using a common path corresponding to the machine device of the same transmission group.
- the network unit 1401 is specifically configured to determine, according to the feature information, a first node and a last node of the common path and a data transmission direction of the common path; and establish a tunnel between the first node and the last node. And storing, in the node of the tunnel, a network address and interface information of a node of the node of the node; and when the data transmission direction is downlink, a node of the tunnel Storing the network address and interface information of the node of the next level of the node; when the data transmission direction is uplink and downlink, the node of the tunnel stores the network of the upper node and the next node of the node Address and interface information.
- the network unit 1401 is further configured to: establish a radio bearer for the device of the same transmission group; set a correspondence between the established radio bearer and the public path in the base station; and in the same path transmission group
- the base station determines the corresponding common path according to the corresponding relationship between the set radio bearer and the public path, and sends the uplink data to the machine server through the determined common path.
- the network unit 1401 is further configured to establish a radio bearer for the device of the same transmission group; set a correspondence between the established radio bearer and the public path in the base station, and set the device information. Corresponding relationship with the radio bearer; when the machine server sends the downlink data through the common path, the base station determines the corresponding radio bearer according to the device information in the downlink data and the corresponding relationship between the set device information and the radio bearer; The base station sends the downlink data to the corresponding machine device through the determined radio bearer.
- the network unit 1401 is further configured to establish a radio bearer for the equipment of the same transmission group, and allocate a network address for the equipment of the same transmission group; and set the established radio bearer in the base station.
- a radio bearer for the equipment of the same transmission group, and allocate a network address for the equipment of the same transmission group; and set the established radio bearer in the base station.
- the base station determines, according to the network address and setting in the downlink data
- Corresponding relationship between the network address of the machine equipment and the radio bearer determines the corresponding radio bearer;
- the downlink data is sent to the corresponding machine device by the determined radio bearer.
- the M2M communication system acquires the common path of the common path corresponding to the machine device of the same transmission group, and establishes the common path according to the feature information, and the machine device of the same transmission group passes the
- the public path performs data transfer with the machine server and releases the common path at the end of the data transfer between the machine device and the machine server of the same transfer group. Therefore, when the MTC Device of the same group and the MTC Server perform data transmission, the public path part only involves the operation of establishing a bearer and releasing the bearer once, which reduces the signaling transmission between the nodes, thereby reducing the network resources occupied by the M2M communication. Improve the processing efficiency of M2M network services.
- the embodiment of the present invention further provides a system for establishing a public path in a wireless communication network, as shown in FIG.
- a mobility management entity 1501 configured to send a session establishment request message to the serving gateway 1502, receive a session establishment response message sent by the serving gateway 1502, and send a bearer setup request message to the base station 1503, where the bearer setup request message carries the service gateway a network address and tunnel endpoint identifier information of 1502; receiving a bearer setup request response sent by the base station 1503 to complete establishment of a public path;
- the service gateway 1502 is configured to receive a session establishment request message sent by the mobility management entity 1501, and send a session establishment response message to the mobility management entity 1501, where the session establishment response message carries a network address and a tunnel of the service gateway 1502. Endpoint identifier information;
- the base station 1503 is configured to receive a bearer setup request message sent by the mobility management entity 1501, and send a bearer setup response message to the mobility management entity 1501.
- the mobility management entity 1501 is specifically configured to send a session establishment request message to the serving gateway 1502 when the common path establishment trigger condition is met, where the public path establishment trigger condition includes a preset configuration condition, and a preset startup Time, or the operation command issued by the network management/maintenance system.
- the common path includes a path between the base station-serving gateway, a path between the base station-service gateway-packet data network gateway, or a path between the base station-serving gateway-packet data network gateway-machine server.
- the public path is a one-way uplink path or a two-way path.
- the public path establishment system in the wireless communication network sends a session establishment request message to the service gateway through the mobility management entity, and receives the message sent by the service gateway. Transmitting a bearer setup response message carrying the network address of the serving gateway and the tunnel endpoint identifier information to the base station, and receiving a bearer setup request message carrying the network address of the serving gateway and the tunnel endpoint identifier information, and receiving the bearer setup request message sent by the base station.
- the bearer setup request response completes the establishment of the public path.
- the common path part only involves the operation of establishing the bearer once, which reduces the signaling transmission between the nodes, thereby reducing the network resources occupied by the M2M communication and improving the M2M.
- the processing efficiency of network services is only involves the operation of establishing the bearer once, which reduces the signaling transmission between the nodes, thereby reducing the network resources occupied by the M2M communication and improving the M2M.
- the embodiment of the present invention further provides a system for establishing a common path in a wireless communication network, as shown in FIG. 16, including:
- the base station 1601 is configured to send an attach request to the mobility management entity 1602; receive an initialization context request or an attach accept message sent by the mobility management entity 1602; send an initialization context response or an attach complete message to the mobility management entity 1602, and complete the public path. Establishing, wherein the initialization context response or attach complete message carries network address and tunnel endpoint identifier information of the base station 1601;
- a mobility management entity 1602 configured to receive an attach request sent by the base station 1601; obtain a network address of the serving gateway and tunnel endpoint identifier information; and send an initialization context request or an attach accept message to the base station 1601, where the initialization context request or The attach accept message carries the network address and tunnel endpoint identifier information of the serving gateway; and receives an initialization context response or an attach complete message sent by the base station 1601.
- the base station 1601 is specifically configured to send an attach request to the mobility management entity 1602 when the common path establishment trigger condition is met, where the public path establishment trigger condition includes a preset configuration condition, a preset startup time, or a network management/ Maintain the operation instructions issued by the system.
- the public path establishment trigger condition includes a preset configuration condition, a preset startup time, or a network management/ Maintain the operation instructions issued by the system.
- the common path includes a path between the base station-serving gateway, a path between the base station-service gateway-packet data network gateway, or a path between the base station-serving gateway-packet data network gateway-machine server.
- the public path is a one-way uplink path or a two-way path.
- the base station sends an attach request to the mobility management entity, and receives the network address and the tunnel end of the service gateway sent by the mobility management entity, and the identifier, An initialization context request or an attach accept message is sent, and an initialization context response or an attach complete message carrying the network address and tunnel endpoint identifier information of the base station is sent to the mobility management entity to complete establishment of the public path. Therefore, when the same group of MTC Device and the MTC Server perform data transmission, the public path part only involves the operation of establishing the bearer once, which reduces the signaling transmission between the nodes, thereby reducing the network resources occupied by the M2M communication and improving the M2M. The processing efficiency of network services.
- the embodiment of the present invention further provides a system for using a public path in a wireless communication network, as shown in FIG. 17, including:
- the device 1701 is configured to send a radio resource control connection request message to the base station 1702, receive a radio resource control connection setup message sent by the base station 1702, and send a radio resource control connection establishment complete message to the base station 1702, where the radio resource control is performed.
- the connection establishment completion message carries a public path association identifier
- a base station 1702 a radio resource control connection request message sent by the receiver device 1701, a radio resource control connection setup message sent to the machine device 1701, and a radio resource control connection establishment complete message sent by the machine device 1701;
- the common path associated identifier in the RRC connection establishment complete message determines a common path corresponding to the machine device 1701; when the uplink data is sent by the receiver device 1701, the pair of the common path is The end node sends the uplink data.
- the base station 1702 is specifically configured to determine, according to the common path associated identifier, a unidirectional uplink common path corresponding to the machine device 1701; when the uplink data sent by the receiver device 1701, pass the unidirectional The row common path sends the uplink data to the opposite node of the one-way uplink public path.
- the base station 1702 is specifically configured to determine, according to the common path associated identifier, a bidirectional public path corresponding to the machine device 1701; when the uplink data sent by the receiver device 1701, the bidirectional public path is The opposite node of the bidirectional public path sends the uplink data.
- the base station 1702 is further configured to: when receiving the downlink data from the opposite end node of the bidirectional public path by using the bidirectional public path, determine, according to the device identifier in the downlink data, the corresponding device device 1701, The determined machine device 1701 transmits the downlink data.
- the public path is a unidirectional uplink common path, including an uplink path between the base station and the serving gateway, an uplink path between the base station-serving gateway and the packet data network gateway, or a base station-serving gateway-grouping Data network gateway - an uplink path between machine servers; or, the public path is a bidirectional public path, including between base station-serving gateways The bidirectional path, the bidirectional path between the base station-serving gateway-packet data network gateway, or the bidirectional path between the base station-serving gateway-packet data network gateway-machine server.
- the storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), or a random storage memory (Random).
- RAM Random Access Memory
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Description
公共路径的建立和使用方法、 M2M的通信方法及系统 本申请要求于 2010 年 12 月 15 日提交中国专利局、 申请号为 201010590124.1 " 的中国专利申请的优先权, 其全部内容通过引用结 合在本申请中。 技术领域 本发明涉及通信领域, 尤其涉及一种无线通信网络中公共路径的 建立和使用方法、 M2M的通信方法及系统。 背景技术
M2M ( machine to machine , 机器对机器)通信业务在未来的通信 技术市场会占据越来越大的比重。 M2M 是无线通信和信息技术的整 合, 可以单向通信和双向通信, 并应用在安全监测、 自动售货机、 货 物跟踪等场景中。
M2M技术的 MTC ( Machine Type Communications , 机器类型通 信) 应用构架主要包含 MTC Device (机器设备)、 MTC Server (机器 服务器), 网络部分(其中包括接入网网元、 核心网网元、 HSS等逻辑 功能体)。 其中, MTC Server中存储 M2M设备或群的相关数据信息, 用以提供 MTC服务,例如, MTC Device是水电读表器, MTC Server 是水电表抄表处理服务器, 其中存储水电读表器的配置信息, 并对抄 表数据进行相应处理。
在实现本发明的过程中,发明人发现现有技术中至少存在如下问 题: 大量的 MTC Device与同一 MTC Server之间进行数据传输的过程 中,即使 MTC Device与 MTC Server之间传输的数据通过相同的通路, 但是每个 MTC Device还是需要分别与该 MTC Server进行建立承载连 接和释放承载连接等操作, 并且, 每个建立承载连接操作或释放承载 连接操作都会涉及在多个网元设备之间传输信令, 因此, 会占用较多 的网络资源, 降低网络业务处理效率。 发明内容
本发明的实施例提供一种无线通信网络中公共路径的建立和使用 方法、 M2M的通信方法及系统, 能够减少占用的网络资源, 提高网络 业务处理效率。
本发明的实施例采用如下技术方案:
一种无线通信网络中公共路径的建立方法, 其特征在于, 包括: 移动管理实体向服务网关发送会话建立请求消息;
接收所述服务网关发送的会话建立响应消息, 所述会话建立响应 消息是对所述会话建立请求消息的响应并携带所述服务网关的网络地 址和隧道端点标识符信息;
向基站发送承载建立请求消息, 所述承载建立请求消息携带所述 服务网关的网络地址和隧道端点标识符信息;
接收所述基站发送的承载建立请求响应完成公共路径的建立。 一种无线通信网络中公共路径的建立方法, 其特征在于, 包括: 基站向移动管理实体发送附着请求;
接收所述移动管理实体发送的初始化上下文请求或附着接受消 息, 所述初始化上下文请求或附着接受消息是对所述附着请求的响应 并携带服务网关的网络地址和隧道端点标识符信息;
向所述移动管理实体发送初始化上下文响应或附着完成消息, 完 成公共路径的建立, 其中所述初始化上下文响应或附着完成消息携带 所述基站的网络地址和隧道端点标识符信息。
一种无线通信网络中单向上行公共路径的使用方法,其特征在于, 包括:
基站接收机器设备发送的无线资源控制连接请求消息;
向所述机器设备发送无线资源控制连接建立消息;
接收所述机器设备发送的无线资源控制连接建立完成消息, 所述 无线资源控制连接建立完成消息携带公共路径关联标识;
根据所述公共路径相关联标识确定与所述机器设备对应的公共路 径;
在接收机器设备发送的上行数据时, 通过所述公共路径向所述公 共路径的对端节点发送所述上行数据。
一种 M2M的通信方法, 包括:
获取与同路传输组的机器设备对应的公共路径的特征信息; 根据所述特征信息建立所述公共路径;
所述同路传输组的机器设备通过所述公共路径与机器服务器进行 数据传输;
在所述同路传输组的机器设备与所述机器服务器之间的数据传输 结束时, 译放所述公共路径。
一种无线通信网络中公共路径的建立系统, 其特征在于, 包括: 移动管理实体, 用于向服务网关发送会话建立请求消息; 接收所 述服务网关发送的会话建立响应消息;向基站发送承载建立请求消息, 所述承载建立请求消息携带所述服务网关的网络地址和隧道端, 标识 符信息;接收所述基站发送的承载建立请求响应完成公共路径的建立; 服务网关,用于接收所述移动管理实体发送的会话建立请求消息; 向所述移动管理实体发送会话建立响应消息, 所述会话建立响应消息 携带所述服务网关的网络地址和隧道端点标识符信息;
基站, 用于接收所述移动管理实体发送的承载建立请求消息; 向 所述移动管理实体发送承载建立响应消息。
一种无线通信网络中公共路径的建立系统, 其特征在于, 包括: 基站, 用于向移动管理实体发送附着请求; 接收所述移动管理实 体发送的初始化上下文请求或附着接受消息; 向所述移动管理实体发 送初始化上下文响应或附着完成消息, 完成公共路径的建立, 其中所 述初始化上下文响应或附着完成消息携带所述基站的网络地址和隧道 端点标识符信息;
移动管理实体, 用于接收所述基站发送的附着请求; 获取服务网 关的网络地址和隧道端点标识符信息; 向所述基站发送初始化上下文 请求或附着接受消息, 所述初始化上下文请求或附着接受消, 携带所 述服务网关的网络地址和隧道端点标识符信息; 接收所述基站发送的 初始化上下文响应或附着完成消息。
一种无线通信网络中单向上行公共路径的使用系统,其特征在于, 包括:
机器设备, 用于向基站发送无线资源控制连接请求消息; 接收所 述基站发送的无线资源控制连接建立消息; 向所述基站发送无线资源 控制连接建立完成消息, 所述无线资源控制连接建立完成消息携带公 共路径关联标识;
基站, 用于接收机器设备发送的无线资源控制连接请求消息; 向 所述机器设备发送无线资源控制连接建立消息; 接收所述机器设备发 送的无线资源控制连接建立完成消息; 根据所述无线资源控制连接建 立完成消息中的公共路径相关联标识确定与所述机器设备对应的公共 路径; 在接收机器设备发送的上行数据时, 通过所述公共路径向所述 公共路径的对端节点发送所述上行数据。
一种 M2M的通信系统, 包括:
网络单元, 用于获取与同路传输组的机器设备对应的公共路径的 特征信息; 根据所述特征信息建立所述公共路径; 在所述同路传输组 的机器设备与机器服务器之间的数据传输结束时,释放所述公共路径; 机器服务器, 用于通过与所述同路传输组的机器设备对应的公共 路径, 与所述同路传输组的机器设备进行数据传输。
本发明实施例提供的无线通信网络中公共路径的建立和使用方 法、 M2M的通信方法及系统, 通过获取与同路传输组的机器设备对应 的公共路径的特征信息, 根据所述特征信息建立所述公共路径, 同路 传输组的机器设备通过所述公共路径与机器服务器进行数据传输, 并 且在同路传输组的机器设备与机器服务器之间的数据传输结束时释放 所述公共路径。 因此, 同一组的 MTC Device与 MTC Server进行数据 传输时, 公共路径部分仅涉及一次建立承载和释放承载的操作, 减少 了节点之间的信令传输, 从而能够减少 M2M 通信时所占用的网络资 源, 提高 M2M网络业务的处理效率。 附图说明 为了更清楚地说明本发明实施例的技术方案, 下面将对实施例描 述中所需要使用的附图作一简单地介绍, 显而易见地, 下面描述中的 附图仅仅是本发明的一些实施例, 对于本领域普通技术人员来讲, 在 不付出创造性劳动的前提下, 还可以根据这些附图获得其他的附图。
图 1为本发明实施例提供的 M2M的通信方法流程示意图; 图 2 为本发明实施例提供的由 MME 触发建立从 eNB 到 MTC Server的双向公共路径的方法流程示意图;
图 3 为本发明实施例提供的由 MME 触发建立从 eNB 到 MTC Server的上行公共路径的方法流程示意图;
图 4 为本发明实施例提供的由 MME 触发建立从 eNB 到 MTC Server的下行公共路径的方法流程示意图;
图 5为本发明实施例提供的由 eNB触发建立从 eNB到 MTC Server 的双向公共路径的方法流程示意图;
图 6为本发明实施例提供的由 eNB触发建立从 eNB到 MTC Server 的上行公共路径的方法流程示意图;
图 7为本发明实施例提供的由 eNB触发建立从 eNB到 MTC Server 的下行公共路径的方法流程示意图;
图 8为本发明实施例提供的使用从 eNB到 MTC Server的公共路 径的通信方法流程示意图;
图 9为本发明实施例提供的使用从 eNB到 P-GW的公共路径的通 信方法流程示意图;
图 10 为本发明实施例提供的由 MME触发删除从 eNB 到 MTC Server的公共路径的方法流程示意图;
图 11 为本发明实施例提供的一种无线通信网络中公共路径的建 立方法的流程示意图;
图 12 为本发明实施例提供的另一种无线通信网络中公共路径的 建立方法的流程示意图;
图 13 为本发明实施例提供的一种无线通信网络中公共路径的使 用方法的流程示意图;
图 14为本发明实施例提供的 M2M的通信系统构成示意图; 图 15 为本发明实施例提供的一种无线通信网络中公共路径的建 立系统的构成示意图;
图 16 为本发明实施例提供的另一种无线通信网络中公共路径的 建立系统的构成示意图;
图 17 为本发明实施例提供的一种无线通信网络中公共路径的使 用系统的构成示意图。 具体实施方式 下面将结合本发明实施例中的附图, 对本发明实施例中的技术方 案进行清楚、 完整地描述, 显然, 所描述的实施例仅仅是本发明一部分 实施例, 而不是全部的实施例。 基于本发明中的实施例, 本领域普通技 术人员在没有做出创造性劳动前提下所获得的所有其他实施例,都属于 本发明保护的范围。
为了能够减少占用的网络资源, 提高网络业务处理效率, 本发明 实施例提供了一种 M2M的通信方法, 如图 1所示, 包括:
101、 获取与同路传输组的机器设备对应的公共路径的特征信息; 在本实施例中, 所述同路传输组的机器设备具有相同的数据传输 路径, 一般具有相同的目的地址 (同一个 MTC Server ) 和 /或 QoS。 其 中, 所述相同的数据传输路径可以是 eNB ( evolved Node B , 演进型基 站 ) 到 S-GW ( Serving Gateway, 服务网关 ) 再到 P-GW ( Packet Data Network Gateway, 分组数据网络网关) , 或者, 只有 eNB到 S-GW, 或者, eNB到 S-GW再到 P-GW 再到 MTC Server,或者, S-GW到 P-GW, 或者, S-GW到 P-GW再到 MTC Server的路径。
所述公共路径的特征信息包括所述公共路径的首节点和末节点以 及所述公共路径的数据传输方向等信息。
102、 根据所述特征信息建立所述公共路径;
在本实施例中, 所述公共路径可以通过节点级信令建立和译放, 或者也可以通过配置建立 (类似 ATM ( Asynchronous Transfer Mode, 异步传输模式 ) 机制的 PVC ( Permanent Virtual Circuit, 永久虚电路 ) 或 SVC ( Switched Virtual Circuit, 交换虚电路) ) 。 并且, 建立和释 放的触发可以是配置触发或者时间触发, 例如, eNB l 下面的 MTC Device组(如水表)只在夜里 3 : 00-4: 00之间随机发送数据, 那么该 公共路径可以在夜里 2: 59触发建立, 3 : 01分触发译放。 当然如果终 端一直发送数据, 那么该公共路径可以在建立后一直不删除, 变为 "永 久路径" 。
举例而言,可以根据所述特征信息确定所述公共路径的首节点和末 节点以及所述公共路径的数据传输方向;在所述首节点和末节点之间建 立隧道; 并且, 在所述数据传输方向为上行时, 所述隧道的节点中存储 所述节点的上一级节点的网络地址和接口信息;在所述数据传输方向为 下行时,所述隧道的节点中存储所述节点的下一级节点的网络地址和接 口信息; 在所述数据传输方向为上下行时, 所述隧道的节点中存储所述 节点的上一级节点和下一级节点的网络地址和接口信息。
在以 3GPP 网络的应用场景中, 建立公共路径可以由 MME ( Mobility Management Entity, 移动管理实体) 触发, 也可以由 eNB 触发, 或者由 P-GW触发, 也可以由其他实体触发并通知 MME、 eNB 或 P-GW去建立对应公共路径。并且,公共路径可以分别是 eNB与 MTC Server之间的路径 (包括 SAE 网络的 eNB到 S-GW再到 P-GW再到 MTC Server, 或 UMTS 网络的 RNC到 SGSN再到 GGSN再到 MTC Server, 本发明以 SAE网络为例, UMTS网络类似, 不再贅述) 、 eNB 与 P-GW之间的路径 (即 eNB到 S-GW再到 P-GW ) 、 S-GW与 P-GW 之间的路径等。另外,公共路径可以是上行路径、下行路径或双向路径。 下面,结合上述不同情况对建立公共路径的过程作进一步详细具体的描 述。
如图 2所示, 本实施例 M2M通信中, 由 MME触发建立从 eNB到 MTC Server的双向公共路径的方法, 包括:
201、 MME 因配置触发或时间触发或其他触发确定需要为一组 MTC Device建立双向的公共路径,向 S-GW发送会话建立请求( Create Session Request ) 消息;
202、 S-GW向 P-GW发送会话建立请求消息, 所述会话建立请求 消息携带 S-GW的 IP地址和 TEID ( Tunnel endpoint ID, 隧道端点标识 符 ) 信息; P-GW接收该会话建立请求消息后, 记录 S-GW的 IP地址 和 TEID信息, 由此建立了 P-GW到 S-GW的下行路径。
其中, 所述 IP地址可以在传递的 GTP消息参数中携带, 也可以在 发送的 IP报文源地址中携带。
另外, 所述会话建立请求消息还可以携带一个信息指示, 该信息指 示用于指示 P-GW是否需要返回 P-GW的 IP地址或 TEID信息。
203、 P-GW与 MTC Server之间建立隧道;
其中, 建立的隧道可以是 IP in IP隧道, 或 GRE ( Generic Routing Encapsulation, 通用路由封装协议) 隧道, 或 IPSEC ( Internet 协议安 全性)隧道等。 另外, 建立隧道的具体方法可以参照现有技术, 在此不 再赘述。
204、 P-GW向 S-GW发送会话建立响应 ( Create Session Response ) 消息,所述会话建立响应消息携带 P-GW的 IP地址和 TEID信息; S-GW 接收该会话建立响应消息后, 记录 P-GW的 IP地址和 TEID信息, 由 此建立了 S-GW到 P-GW的上行路径。
205、 S-GW向 MME发送会话建立响应消息, 所述会话建立响应 消息携带 S-GW的 IP地址和 TEID信息; MME接收该会话建立响应消 息后, 从接收的会话建立响应消息中获取 S-GW的 IP地址和 TEID信 息。
206、 MME向 eNB发送 载建立请求消息, 所述 载建立请求消 息携带 S-GW的 IP地址和 TEID信息; eNB接收该承载建立请求消息 后 , 记录 S-GW的 IP地址和 TEID信息 , 由此建立了 eNB到 S-GW的 上行路径。
207、 eNB向 MME发送 载建立响应消息, 所述 载建立响应消 息携带 eNB的 IP地址和 TEID信息; MME接收该 7 载建立响应消息 后, 从该承载建立响应消息中获取 eNB的 IP地址和 TEID信息。
208、 MME向 S-GW发送承载修改请求消息, 所述承载修改请求 消息携带 eNB的 IP地址和 TEID信息; S-GW接收该承载修改请求消 息后 , 记录该 eNB的 IP地址和 TEID信息, 由此建立了 S-GW到 eNB 的下行路径。
209、 S-GW向 MME发送承载修改响应消息。
另外,需要建立的公共路径是 eNB到 MTC Server之间的双向路径 中的部分路径时 ,可以通过适当省略图 2所描述的实施例中的某些步骤 来实现。 例如, 如果需要建立的公共路径是 eNB到 P-GW的双向路径 , 则在图 2所描述的实施例中省略步骤 203即可建立该公共路径。如果需 要建立的公共路径是 eNB到 S-GW的双向路径, 则在图 2所描述的实 施例中省略步骤 202-204即可建立该公共路径。如果需要建立的公共路 径是 S-GW到 P-GW的双向路径, 则在图 2所描述的实施例中省略步 骤 203、 206-209即可建立该公共路径。 其他实施例类似, 不再贅述。
如图 3所示, 本实施例 M2M通信中, 由 MME触发建立从 eNB到 MTC Server的上行公共路径的方法, 包括:
301、 MME 因配置触发或时间触发或其他触发确定需要为一组 MTC Device建立上行的公共路径, 向 S-GW发送会话建立请求消息;
302、 S-GW向 P-GW发送会话建立请求消息。
其中, 所述会话建立请求消息还可以携带一个信息指示, 该信息指 示用于指示 P-GW是否需要返回 P-GW的 IP地址或 TEID信息。
303、 P-GW与 MTC Server之间建立隧道;
其中, 建立的隧道可以是 IP in IP隧道, 或 GRE (通用路由封装协 议) 隧道, 或 IPSEC 隧道等。 另外, 建立隧道的具体方法可以参照现 有技术, 在此不再贅述。
304、 P-GW向 S-GW发送会话建立响应消息, 所述会话建立响应 消息携带 P-GW的 IP地址和 TEID信息; S-GW接收该会话建立响应消 息后 , 记录 P-GW的 IP地址和 TEID信息 , 由此建立了 S-GW到 P-GW 的上行路径。
305、 S-GW向 MME发送会话建立响应消息, 所述会话建立响应 消息携带 S-GW的 IP地址和 TEID信息; MME接收该会话建立响应消 息后, 从接收的会话建立响应消息中获取 S-GW的 IP地址和 TEID信 息。
306、 MME向 eNB发送承载建立请求消息, 所述承载建立请求消 息携带 S-GW的 IP地址和 TEID信息; eNB接收该承载建立请求消息 后 , 记录 S-GW的 IP地址和 TEID信息 , 由此建立了 eNB到 S-GW的 上行路径。
其中, 所述承载建立请求消息还可以携带一个信息指示, 该信息指 示用于指示 eNB不需要向 S-GW返回该 eNB的 IP地址或 TEID信息。
307、 eNB向 MME发送 载建立响应消息。
另外,需要建立的公共路径是 eNB到 MTC Server之间的上行路径 中的部分路径时,可以通过适当省略图 3所描述的实施例中的某些步骤 来实现。 例如, 如果需要建立的公共路径是 eNB到 P-GW的上行路径, 则在图 3所描述的实施例中省略步骤 303即可建立该公共路径。
如图 4所示, 本实施例 M2M通信中, 由 MME触发建立从 eNB到 MTC Server的下行公共路径的方法, 包括:
401、 MME 因配置触发或时间触发或其他触发确定需要为一组 MTC Device建立下行的公共路径, 向 S-GW发送会话建立请求消息;
402、 S-GW向 P-GW发送会话建立请求消息, 所述会话建立请求 消息携带 S-GW的 IP地址和 TEID信息; P-GW接收该会话建立请求消 息后 , 记录 S-GW的 IP地址和 TEID信息 , 由此建立了 P-GW到 S-GW 的下行路径。
其中, 所述 IP地址可以在传递的 GTP消息参数中携带, 也可以在 发送的 IP报文源地址中携带。
另外, 所述会话建立请求消息还可以携带一个信息指示, 该信息指 示用于指示 P-GW不需要返回 P-GW的 IP地址或 TEID信息。
403、 P-GW与 MTC Server之间建立隧道;
其中, 建立的隧道可以是 IP in IP隧道, 或 GRE隧道, 或 IPSEC 隧道等。另外,建立隧道的具体方法可以参照现有技术,在此不再贅述。
404、 P-GW向 S-GW发送会话建立响应消息。
405、 S-GW向 MME发送会话建立响应消息, 所述会话建立响应 消息可以携带一个信息指示,该信息指示用于指示 eNB需要返回 P-GW 的 IP地址或 TEID信息。
406、 MME向 eNB发送 载建立请求消息, 所述 载建立请求消 息携带一个信息指示, 该信息指示用于指示 eNB需要返回 P-GW的 IP 地址或 TEID信息。
407、 eNB向 MME发送 载建立响应消息, 所述 载建立响应消 息携带 eNB的 IP地址和 TEID信息; MME接收该承载建立响应消息 后, 从该承载建立响应消息中获取 eNB的 IP地址和 TEID信息。
408、 MME向 S-GW发送承载修改请求消息, 所述承载修改请求 消息携带 eNB的 IP地址和 TEID信息; S-GW接收该承载修改请求消 息后 , 记录该 eNB的 IP地址和 TEID信息, 由此建立了 S-GW到 eNB 的下行路径。
409、 S-GW向 MME发送承载修改响应消息。
另外,需要建立的公共路径是 eNB到 MTC Server之间的下行路径 中的部分路径时,可以通过适当省略图 4所描述的实施例中的某些步骤 来实现。 例如, 如果需要建立的公共路径是 eNB到 P-GW的下行路径, 则在图 4所描述的实施例中省略步骤 403即可建立该公共路径。
如图 5所示, 本实施例 M2M通信中, 由 eNB触发建立从 eNB到 MTC Server的双向公共路径的方法, 包括:
501、 eNB因配置触发或时间触发或其他触发确定需要为一组 MTC Device建立双向的公共路径, eNB可以模拟 UE, 类似 UE 已经接入 eNB一样, 向 MME发送附着请求 ( Attach Request ) ;
502、 MME接收该附着请求后, 向 S-GW发送会话建立请求消息;
503、 S-GW接收该会话建立请求消息后, 向 P-GW发送会话建立 请求消息,所述会话建立请求消息携带 S-GW的 IP地址和 TEID信息; P-GW接收该会话建立请求消息后, 记录 S-GW的 IP地址和 TEID信 息, 由此建立了 P-GW到 S-GW的下行路径。
其中, 所述 IP地址可以在传递的 GTP消息参数中携带, 也可以在 发送的 IP报文源地址中携带。
另外, 所述会话建立请求消息还可以携带一个信息指示, 该信息指 示用于指示 P-GW是否需要返回 P-GW的 IP地址或 TEID信息。
504、 P-GW与 MTC Server之间建立隧道;
其中, 建立的隧道可以是 IP in IP隧道, 或 GRE隧道, 或 IPSEC 隧道等。另外,建立隧道的具体方法可以参照现有技术,在此不再贅述。
505、 P-GW向 S-GW发送会话建立响应消息, 所述会话建立响应 消息携带 P-GW的 IP地址和 TEID信息; S-GW接收该会话建立响应消 息后 , 记录 P-GW的 IP地址和 TEID信息 , 由此建立了 S-GW到 P-GW 的上行路径。
506、 S-GW向 MME发送会话建立响应消息, 所述会话建立响应 消息携带 S-GW的 IP地址和 TEID信息; MME接收该会话建立响应消 息后, 从接收的会话建立响应消息中获取 S-GW的 IP地址和 TEID信 息。
507、 MME向 eNB发送初始化上下文请求 /附着接受( Initial Context Setup Request/Attach Accept ) 消息, 所述初始化上下文请求 /附着接受 消息携带 S-GW的 IP地址和 TEID信息; eNB接收该初始化上下文请 求 /附着接受消息后, 记录 S-GW的 IP地址和 TEID信息, 由此建立了 eNB到 S-GW的上行路径。
508、 eNB向 MME发送初始化上下文响应 /附着完成( Initial Context Setup Response/Attach Complete )消息, 所述初始化上下文响应 /附着完
成消息携带 eNB的 IP地址和 TEID信息; MME接收该初始化上下文 响应 /附着完成消息后, 从该初始化上下文响应 /附着完成消息中获取 eNB的 IP地址和 TEID信息。
509、 MME向 S-GW发送承载修改请求消息, 所述承载修改请求 消息携带 eNB的 IP地址和 TEID信息; S-GW接收该承载修改请求消 息后 , 记录该 eNB的 IP地址和 TEID信息, 由此建立了 S-GW到 eNB 的下行路径。
510、 S-GW向 MME发送承载修改响应消息。
另外,需要建立的公共路径是 eNB到 MTC Server之间的路径中的 部分双向路径时,可以通过适当省略图 5所描述的实施例中的某些步骤 来实现。 例如, 如果需要建立的公共路径是 eNB到 P-GW的双向路径, 则在图 5所描述的实施例中省略步骤 504即可建立该公共路径。如果需 要建立的公共路径是 eNB到 S-GW的双向路径, 则在图 5所描述的实 施例中省略步骤 503-505即可建立该公共路径。如果需要建立的公共路 径是 S-GW到 P-GW的双向路径, 则在图 5所描述的实施例中省略步 骤 504、 507-510即可建立该公共路径。
如图 6所示, 本实施例 M2M通信中, 由 eNB触发建立从 eNB到 MTC Server的上行公共路径的方法, 包括:
601、 eNB因配置触发或时间触发或其他触发确定需要为一组 MTC Device建立上行的公共路径, 向 MME发送附着请求;
602、 MME接收该附着请求后, 向 S-GW发送会话建立请求消息;
603、 S-GW接收该会话建立请求消息后, 向 P-GW发送会话建立 请求消息。
其中, 所述会话建立请求消息还可以携带一个信息指示, 该信息指 示用于指示 P-GW是否需要返回 P-GW的 IP地址或 TEID信息。
604、 P-GW与 MTC Server之间建立隧道;
其中, 建立的隧道可以是 IP in IP隧道, 或 GRE隧道, 或 IPSEC 隧道等。另外,建立隧道的具体方法可以参照现有技术,在此不再贅述。
605、 P-GW向 S-GW发送会话建立响应消息, 所述会话建立响应 消息携带 P-GW的 IP地址和 TEID信息; S-GW接收该会话建立响应消 息后 , 记录 P-GW的 IP地址和 TEID信息 , 由此建立了 S-GW到 P-GW 的上行路径。
606、 S-GW向 MME发送会话建立响应消息, 所述会话建立响应 消息携带 S-GW的 IP地址和 TEID信息; MME接收该会话建立响应消 息后, 从接收的会话建立响应消息中获取 S-GW的 IP地址和 TEID信 息。
607、 MME向 eNB发送初始化上下文请求 /附着接受消息, 所述初 始化上下文请求 /附着接受消息携带 S-GW的 IP地址和 TEID信息; eNB 接收该初始化上下文请求 /附着接受消息后, 记录 S-GW 的 IP 地址和 TEID信息 , 由此建立了 eNB到 S-GW的上行路径。
608、 eNB向 MME发送初始化上下文响应 /附着完成消息。
另外,需要建立的公共路径是 eNB到 MTC Server之间的上行路径 中的部分路径时,可以通过适当省略图 6所描述的实施例中的某些步骤 来实现。 例如, 如果需要建立的公共路径是 eNB到 P-GW的上行路径, 则在图 6所描述的实施例中省略步骤 604即可建立该公共路径。
如图 7所示, 本实施例 M2M通信中, 由 eNB触发建立从 eNB到 MTC Server的下行公共路径的方法, 包括:
701、 eNB因配置触发或时间触发或其他触发确定需要为一组 MTC Device建立下行的公共路径, 向 MME发送附着请求;
702、 MME接收该附着请求后, 向 S-GW发送会话建立请求消息;
703、 S-GW接收该会话建立请求消息后, 向 P-GW发送会话建立 请求消息,所述会话建立请求消息携带 S-GW的 IP地址和 TEID信息; P-GW接收该会话建立请求消息后, 记录 S-GW的 IP地址和 TEID信 息, 由此建立了 P-GW到 S-GW的下行路径。
其中, 所述 IP地址可以在传递的 GTP消息参数中携带, 也可以在 发送的 IP报文源地址中携带。
另外, 所述会话建立请求消息还可以携带一个信息指示, 该信息指 示用于指示 P-GW不需要返回 P-GW的 IP地址或 TEID信息。
704、 P-GW与 MTC Server之间建立隧道;
其中, 建立的隧道可以是 IP in IP隧道, 或 GRE隧道, 或 IPSEC 隧道等。另外,建立隧道的具体方法可以参照现有技术,在此不再贅述。
705、 P-GW向 S-GW发送会话建立响应消息。
706、 S-GW向 MME发送会话建立响应消息, 所述会话建立响应 消息携带一个信息指示, 该信息指示用于指示 eNB需要返回 P-GW的
IP地址或 TEID信息。
707、 MME向 eNB发送初始化上下文请求 /附着接受消息, 所述初 始化上下文请求 /附着接受消息携带一个信息指示, 该信息指示用于指 示 eNB需要返回 P-GW的 IP地址或 TEID信息。
708、 eNB向 MME发送初始化上下文响应 /附着完成消息, 所述初 始化上下文响应 /附着完成消息携带 eNB的 IP地址和 TEID信息; MME 接收该初始化上下文响应 /附着完成消息后, 从该初始化上下文响应 /附 着完成消息中获取 eNB的 IP地址和 TEID信息。
709、 MME向 S-GW发送承载修改请求消息, 所述承载修改请求 消息携带 eNB的 IP地址和 TEID信息; S-GW接收该承载修改请求消 息后 , 记录该 eNB的 IP地址和 TEID信息, 由此建立了 S-GW到 eNB 的下行路径。
710、 S-GW向 MME发送承载修改响应消息。
另外,需要建立的公共路径是 eNB到 MTC Server之间的下行路径 中的部分路径时,可以通过适当省略图 7所描述的实施例中的某些步骤 来实现。 例如, 如果需要建立的公共路径是 eNB到 P-GW的下行路径, 则在图 7所描述的实施例中省略步骤 704即可建立该公共路径。
103、 所述同路传输组的机器设备通过所述公共路径与机器服务器 进行数据传输;
举例而言, 所述同路传输组的机器设备接入时, 为所述同路传输组 的机器设备建立无线承载; 在公共路径为上行路径或双向路径时,基站 中设定建立的无线承载与公共路径的对应关系;并在所述同路传输组的 机器设备通过建立的无线承载发送上行数据时,基站根据设定的无线承 载与公共路径的对应关系确定对应的公共路径,将所述上行数据通过确 定的公共路径发送给机器服务器。 在公共路径为下行路径或双向路径 时,基站中设定建立的无线承载与所述公共路径的对应关系, 并设定机 器设备信息或网络地址与无线承载的对应关系;在机器服务器通过所述 公共路径发送下行数据时,基站根据所述下行数据中的机器设备信息以 及设定的机器设备信息与无线承载的对应关系, 或者,根据所述下行数 据中的网络地址以及设定的机器设备的网络地址与无线承载的对应关 系,确定对应的无线承载;基站通过确定的无线承载将所述下行数据发 送给对应的机器设备。如, 可以通过在基站为不同机器设备的不同无线
承载建立过滤器 (filtering ) , 该过滤器设置不同机器设备的属性, 如 IP地址和 /或设备标识和 /或通信端口等信息, 一套属性与一个无线承载 对应。 基站通过该过滤器决定将下行数据发往哪个无现承载。
如果建立的是 eNB-P-GW公共路径,那么在 MTC Device发送数据 前需要获取 MTC Device的 IP地址, 该 IP地址可以是附着时获取, 也 可以在发送数据前接入网络现分配。 而如果建立的是 eNB-MTC Server 的公共路径, 那么可以不为 MTC Device分配 IP地址, MTC Server从 一条相同的通路上收到各个 MTC Device的数据, 仅通过数据中包含的 应用标识或设备标识来区分不同的 MTC Device。下面,以 eNB到 MTC Server以及 eNB到 P-GW的公共路径为例, 对使用公共路径的通信方 法作进一步详细具体的描述。
如图 8所示, 本实施例 M2M通信中, 使用从 eNB到 MTC Server 的公共路径的通信方法, 包括:
801、 MTC Device 向 eNB 发送无线资源控制连接请求 ( RRC Connection Request ) 消息。
802、 eNB接收该无线资源控制连接请求消息后, 向 MTC Device 发送无线资源控制连接建立 ( RRC Connection Setup ) 消息。
803、 MTC Device接收该无线资源控制连接建立消息后, 向 eNB 发送无线资源控制连接建立完成 ( RRC Connection Setup Complete ) 消 息, 所述无线资源控制连接建立完成消息携带公共路径关联标识。
其中, 所述公共路径关联标识包括组 ID或设备 ID或公共路径 ID 等。 并且,还可以在所述无线资源控制连接请求消息中携带 NAS消息, 此时, 由于 载已经建立, eNB可以不将 NAS传递给 MME, 甚至不 与 MME进行任何交互 , 或只交互安全鉴权操作而不必由 MME进行承 载建立操作。
另外,也可以不在无线资源控制连接建立完成消息中携带公共路径 关联标识,而是在所述无线资源控制连接请求消息中携带公共路径关联 标识。
804、 eNB向 MTC Device发送无线承载建立 ( RB Establish )消息。 eNB根据该公共路径关联标识将该 MTC Device与公共路径关联起来。
举例说明, 当公共路径为上行路径, 即 MTC Device 仅向 MTC Server上传数据时, eNB可以根据公共路径关联标识将为 MTC Device
建立的 RB ( Radio Bearer, 无线承载) 与 MTC Device所对应的公共路 径对应。 当公共路径为下行路径, 即 MTC Device仅从 MTC Server下 载数据时, eNB 可以 居公共路径关联标识将为 MTC Device建立的 RB 与 MTC Device 所对应的公共路径对应, 并将设备 ID 与为 MTC Device建立的 RB对应。 当公共路径为双向路径, 即 MTC Device既向 MTC Server上传数据又从 MTC Server下载数据时, eNB可以根据公共 路径关联标识将为 MTC Device建立的 RB与 MTC Device所对应的公 共路径对应, 并将设备 ID与为 MTC Device建立的 RB对应。
805、 MTC Device通过 RB发送上行数据, eNB接收该上行数据后, 通过对应的公共路径将该上行数据传送给 MTC Server。
在本实施例中, 公共路径为 eNB到 MTC Server的路径, 此时可以 不获取 MTC Device的 IP地址 , MTC Server从同一条通路上收到各个 MTC Device的数据后, MTC Server仅通过数据中包含的应用标识或设 备标识即可区分不同的 MTC Device。 因此, 所述上行数据可以是没有 IP头的原始数据, 也可以是添加了 IP头的数据。
举例说明 , 假设多个 MTC Device接入网络, 他们属于同一个组, 使用相同的公共路径, eNB为这些 MTC Device建立各自的 RB ,在 MTC Device通过 RB上传数据时, eNB通过该 RB接收数据后, 通过对应的 公共路径将接收的数据上传给 MTC Server。 并且, MTC Server还可以 根据数据中的设备 ID 或应用层标识区分出数据到底来自哪个 MTC Device。
806、 MTC Server通过对应的公共路径发送下行数据, eNB接收该 下行数据后, 根据该下行数据中的设备 ID确定对应的 RB, 并通过该 RB将该下行数据传送给对应的 MTC Device。
在本实施例中, 所述下行数据可以是没有 IP头的原始数据, 也可 以是添加了 IP头的数据。
举例说明, 在 MTC Server下发数据时 , eNB通过对应的公共路径 接收的数据, 根据接收的数据中携带的设备 ID确定对应的 RB , 并通 过该 RB向 MTC Device下发数据。
在本实施例中, MTC Device还可以不携带任何 NAS消息, 或者, eNB还可以在收到 RRC连接请求消息后直接建立 RB。
如图 9所示, 本实施例 M2M通信中, 使用从 eNB到 P-GW的公 共路径的通信方法, 包括:
901、 MTC Device向 eNB发送无线资源控制连接请求消息, 所述 无线资源控制连接请求消息携带公共路径关联标识。
其中, 所述公共路径关联标识包括组 ID或设备 ID或公共路径 ID 等。
在本实施例中, P-GW以外到 MTC Server是 IP网络, 因此, MTC Device发出的数据出了 P-GW时必须具有 IP包头。
902、 eNB向 MTC Device发送无线承载建立消息。 eNB根据该公 共路径关联标识将该 MTC Device与公共路径关联起来。
当公共路径为上行路径 , 即 MTC Device仅向 MTC Server上传数 据时, eNB可以 居公共路径关联标识将为 MTC Device建立的 RB与 MTC Device所对应的公共路径对应。 当公共路径为下行路径, 即 MTC Device仅从 MTC Server下载数据时, eNB可以根据公共路径关联标识 将为 MTC Device建立的 RB与 MTC Device所对应的公共路径对应, 并将设备 ID与为 MTC Device建立的 RB对应。 当公共路径为双向路 径, 即 MTC Device既向 MTC Server上传数据又从 MTC Server下载数 据时, eNB可以 居公共路径关联标识将为 MTC Device建立的 RB与 MTC Device所对应的公共路径对应,并将设备 ID或 MTC Device的 IP 地址信息与为 MTC Device建立的 RB对应。
903、 MTC Device通过 RB发送上行数据, eNB接收该上行数据后, 通过对应的公共路径将该上行数据传送给 P-GW, P-GW将该上行数据 传送给 MTC Server。
只有在公共路径为 eNB到 MTC Server的路径时, 才可以不获取 MTC Device的 IP地址, 这是因为 MTC Server从同一条通路上收到各 个 MTC Device的数据后, MTC Server仅通过数据中包含的应用标识或 设备标识即可区分不同的 MTC Device„而本实施例中,公共路径为 eNB 到 P-GW的路径, 此时需要获取 MTC Device的 IP地址, 并在上行数 据中添加发送该上行数据的 MTC Device的 IP地址。 并且, 该 IP地址 可以是在附着时获取, 也可以是在发送数据前接入网络现分配。
举例说明, eNB可以在 MTC Device接入时给各 MTC Device分
配相同的或者不同的 IP地址。 各 MTC Device通过 RB向 eNB发送携 带其分配到的 IP地址的数据, eNB接收该上行数据后, 通过对应的公 共路径将该上行数据传送给 P-GW, P-GW根据该上行数据中的 IP地址 将该上行数据发送给对应的 MTC Server。
或者, eNB不为 MTC Device分配 IP地址, 而是在 MTC Device 通过 RB发送原始的上行数据时在该上行数据上添加 IP 包头, 目的地 址为 MTC Server„ eNB 通过对应的公共路径将该上行数据传送给 P-GW, P-GW 根据该上行数据中的目的地址将该上行数据发送给对应 的 MTC Server。
或者, eNB不为 MTC Device分配 IP地址, 在 MTC Device通过 RB发送原始的上行数据时, eNB通过对应的公共路径将该上行数据传 送给 P-GW, P-GW接收该上行数据后在该上行数据中添加 IP包头, 向对应的 MTC Server发送添加有 IP包头的上行数据。
904、 MTC Server发送下行数据, P-GW接收该下行数据后, 通过 对应的公共路径将该下行数据传送给 eNB , eNB接收该下行数据后, 根据该下行数据中的 IP地址或设备 ID确定对应的 RB , 并通过该 RB 将该下行数据传送给对应的 MTC Device„
举例说明 , eNB可以在接入时为各 MTC Device分配不同的 IP地 址。 eNB设定 MTC Device的 IP五元组信息 (即源 IP地址、 目的 IP 地址、 源端口号、 目的端口号、 协议名称等)与 RB的对应关系, P-GW 设定 MTC Device的 IP地址段与公共路径的对应关系。 MTC Server发 送携带 IP地址信息的下行数据, P-GW接收该下行数据后, 根据该下 行数据中的 IP地址信息确定对应的公共路径, 通过该公共路径将该下 行数据传送给 eNB , eNB接收该下行数据后, 根据该下行数据中的 IP 地址信息确定对应的 RB , 并通过该 RB 将该下行数据传送给对应的 MTC Device。例如,假设一个 eNB下有共用一个公共路径的组设备 1000 个, 他们将集中在凌晨 3 : 00-4: 00发送数据, 但不会一窝蜂的同时接 入这些设备, 而是打散随机的接入这些设备,每个设备被接入 5分钟进 行数据传递, 传递结束后就不会再接入该设备了。 eNB 为该组设备保 留 150个 IP地址, 每个接入的设备接入时分配一个 IP地址, 接入结束 后释放该 IP地址,之后其他设备被接入时将释放的 IP地址分配给这些
设备使用。 因此, 原则上同一时间内最多允许 150个设备同时接入。 在 凌晨 2: 59建立公共路径后, P-GW中记录该 150个 IP地址与该公共 路径的对应关系 , eNB每次为 MTC Device分配了一个 IP地址后就将 该 MTC Device对应的 RB与该 IP地址对应。 当一个 MTC Device发送 了上行数据 (该数据的源地址是分配给它的 IP 地址, 源端口是 MTC Device分配的端口号, 目的地址是 MTC Server的 IP地址, 目的端口是 MTC Sever的端口 )后, MTC Server要响应这个 MTC Device, 就会回 复一个数据, 该回复的数据的 IP 包头中的目的地址是该 MTC Device 的 IP地址, 目的端口是 MTC Device的端口, P-GW接收该回复的数据 后, 根据目的地址 (即 MTC Device的 IP地址) 和目的端口等信息判 定该数据应该被发送到该公共路径而不是其他路径, 然后, P-GW通过 公共路径向 eNB发送该数据。 eNB接收该数据后, 根据目的地址 (即 MTC Device的 IP地址 )和目的端口等信息确定与该 MTC Device对应 的 RB, 通过该 RB向该 MTC Device发送该数据。
或者, eNB也可以给各 MTC Device分配相同的 IP地址, 各 MTC Device将 IP地址相关数据信息发送给 eNB。 eNB设定 MTC Device的 ID与 RB的对应关系, P-GW设定 MTC Device的 IP地址与公共路径的 对应关系。 MTC Server发送携带分配给 MTC Device的 IP地址的下行 数据, P-GW接收该下行数据后, 根据该下行数据中 MTC Device的 IP 地址确定公共路径, 并通过该公共路径将该下行数据传送给 eNB。 eNB 接收该下行数据后, 根据该下行数据中的设备 ID确定对应的 RB , 并 通过该 RB将该下行数据传送给对应的 MTC Device。
或者, MTC Server发送携带某一特定 IP地址的下行数据, P-GW 接收该下行数据后, 根据该下行数据中的 IP地址确定公共路径, 并通 过该公共路径将该下行数据传送给 eNB。 eNB接收该下行数据后, 根 据该下行数据中的设备 ID确定对应的 RB ,并通过该 RB将该下行数据 传送给对应的 MTC Device。
以上介绍了基于传统的有连接 (即无线接口存在 RB ) 的方法。 另 外, 还可以采用基于无连接的方法使用公共路径, 如 MTC Device不会 发送 RRC连接请求, 以建立信令连接和 RB数据连接, 而是直接在某 个时频资源向 eNB发送数据, eNB根据收到的数据中的标识信息 (如 组 ID )确定相关联的公共路径, 通过该公共路径将该数据发送给 MTC
Server或 P-GW。 而 eNB通过公共路径从 MTC Server或 P-GW接收数 据后, 根据该数据中的标识信息或 IP地址直接在某个时频资源向对应 MTC Device发送该数据。
104、 在所述同路传输组的机器设备与所述机器服务器之间的数据 传输结束时, 释放所述公共路径。
下面以 MME 触发删除公共路径为例对删除公共路径的过程作进 一步详细具体的描述。
如图 10所示, 本实施例 M2M通信中, 由 MME触发删除从 eNB 到 MTC Server的公共路径的方法, 包括:
1001、 MME因配置触发或时间触发或其他触发确定需要删除一个 为一组 MTC Device所建立的公共路径, 向 S-GW发送会话删除请求
( Delete Session Request ) 消息;
1002、 S-GW向 P-GW发送会话删除请求消息;
1003、 释放 P-GW与 MTC Server之间的隧道;
1004、 P-GW向 S-GW发送会话删除响应( Delete Session Response ) 消息。
1005、 S-GW向 MME发送会话删除响应消息。
1006、 MME向 eNB发送承载释放请求 ( Release Bearer Request ) 消息;
1007、 eNB向 MME发送承载释放响应 ( Release Bearer Response ) 消息。
另外,建立的公共路径是 eNB到 MTC Server之间的路径中的部分 路径时,可以通过适当省略图 10所描述的实施例中的某些步骤来实现。 例如, 如果建立的公共路径是 eNB到 P-GW的路径, 则在图 10所描述 的实施例中省略步骤 1003即可译放该公共路径。 如果建立的公共路径 是 eNB 到 S-GW 的路径, 则在图 10 所描述的实施例中省略步骤 1002-1004即可释放该公共路径。如果建立的公共路径是 S-GW到 P-GW 的路径, 则在图 10所描述的实施例中省略步骤 1003、 1006-1007即可 释放该公共路径。
另外, 当 eNB触发建立的公共路径需要删除时, eNB可以模仿一 个正常 UE的承载删除过程或分离 (Detach ) 过程进行删除公共路径。
本发明实施例提供的 M2M的通信方法, 通过获取与同路传输组的
机器设备对应的公共路径的特征信息,根据所述特征信息建立所述公共 路径,同路传输组的机器设备通过所述公共路径与机器服务器进行数据 传输,并且在同路传输组的机器设备与机器服务器之间的数据传输结束 时释放所述公共路径。 因此, 同一组的 MTC Device与 MTC Server进 行数据传输时, 公共路径部分仅涉及一次建立承载和释放承载的操作, 减少了节点之间的信令传输, 从而能够减少 M2M通信时所占用的网络 资源, 提高 M2M网络业务的处理效率。
另外,本发明实施例还提供了一种无线通信网络中公共路径的建立 方法, 如图 1 1所示, 包括:
1101、 移动管理实体向服务网关发送会话建立请求消息;
举例而言, 移动管理实体会在满足公共路径建立触发条件时, 向服 务网关发送会话建立请求消息,其中所述公共路径建立触发条件包括预 先设置的配置条件, 预先设置的启动时间, 或者网管 /维护系统下发的 操作指令。
在本实施例中, 建立的公共路径包括基站 -服务网关之间的路径, 基站-服务网关-分组数据网络网关之间的路径, 或者基站-服务网关-分 组数据网络网关 -机器服务器之间的路径。 另外, 建立的公共路径为单 向上行路径或双向路径。
1102、 移动管理实体接收所述服务网关发送的会话建立响应消息, 所述会话建立响应消息是对所述会话建立请求消息的响应并携带所述 服务网关的网络地址和隧道端点标识符信息;
举例而言,以建立的公共路径是 eNB ~ S-GW ~ P-GW ~ MTC Server 之间的双向路径为例, S-GW接收 MME发送的会话建立请求消息后, 向 P-GW发送会话建立请求消息,所述会话建立请求消息携带 S-GW的 IP地址和 TEID信息。 P-GW接收 S-GW发送的会话建立请求消息后, 记录所述会话建立请求消息中的 S-GW的 IP地址和 TEID信息。 P-GW 与 MTC Server之间建立隧道。 并且, P-GW向 S-GW发送会话建立响 应消息, 所述会话建立响应消息携带 P-GW的 IP地址和 TEID信息。 S-GW接收 P-GW发送的会话建立响应消息后,记录所述会话建立响应 消息中的 P-GW的 IP地址和 TEID信息。 S-GW向 MME发送会话建立 响应消息, 所述会话建立响应消息携带 S-GW的 IP地址和 TEID信息。
1103、移动管理实体向基站发送承载建立请求消息, 所述承载建立
请求消息携带所述服务网关的网络地址和隧道端点标识符信息;
1 104、移动管理实体接收所述基站发送的承载建立请求响应完成公 共路径的建立。
举例而言, 以公共路径包括 MME ~ eNB的路径为例 , MME接收 eNB发送的承载建立响应消息后, 向 S -G W发送承载修改请求消息, 所述 载爹改请求消息 eNB的 IP地址和 TEID信息。 S-GW接收该 载修改请求消息后 , 记录该 eNB的 IP地址和 TEID信息 , 向 MME发 送承载修改响应消息。
本实施例提供的无线通信网络中公共路径的建立方法,通过移动管 理实体向服务网关发送会话建立请求消息,并接收所述服务网关发送的 携带所述服务网关的网络地址和隧道端点标识符信息的会话建立响应 消息,向基站发送携带所述服务网关的网络地址和隧道端点标识符信息 的承载建立请求消息,并接收所述基站发送的承载建立请求响应完成公 共路径的建立。 因此, 同一组的 MTC Device与 MTC Server进行数据 传输时,公共路径部分仅涉及一次建立承载的操作, 减少了节点之间的 信令传输, 从而能够减少 M2M通信时所占用的网络资源, 提高 M2M 网络业务的处理效率。
另外,本发明实施例还提供了一种无线通信网络中公共路径的建立 方法, 如图 12所示, 包括:
1201、 基站向移动管理实体发送附着请求;
举例而言,基站会在满足公共路径建立触发条件时, 向移动管理实 体发送附着请求, 所述公共路径建立触发条件包括预先设置的配置条 件, 预先设置的启动时间, 或者网管 /维护系统下发的操作指令。
在本实施例中, 建立的公共路径包括基站 -服务网关之间的路径, 基站-服务网关-分组数据网络网关之间的路径, 或者基站-服务网关-分 组数据网络网关 -机器服务器之间的路径。 另外, 建立的公共路径为单 向上行路径或双向路径。
1202、基站接收所述移动管理实体发送的初始化上下文请求或附着 接受消息,所述初始化上下文请求或附着接受消息是对所述附着请求的 响应并携带服务网关的网络地址和隧道端点标识符信息;
举例而言,以建立的公共路径是 eNB ~ S-GW ~ P-GW ~ MTC Server 之间的双向路径为例, MME接收该附着请求后, 向 S-GW发送会话建
立请求消息。 S-GW接收该会话建立请求消息后, 向 P-GW发送会话建 立请求消息, 所述会话建立请求消息携带 S-GW的 IP地址和 TEID信 息。 P-GW接收该会话建立请求消息后 , 记录 S-GW的 IP地址和 TEID 信息, P-GW与 MTC Server之间建立隧道, P-GW向 S-GW发送会话 建立响应消息, 所述会话建立响应消息携带 P-GW的 IP地址和 TEID 信息。 S-GW接收该会话建立响应消息后 ,记录 P-GW的 IP地址和 TEID 信息, 向 MME 发送会话建立响应消息, 所述会话建立响应消息携带 S-GW的 IP地址和 TEID信息。 MME接收该会话建立响应消息后, 向 eNB 发送初始化上下文请求或附着接受消息, 所述初始化上下文请求 或附着接受消息携带 S-GW的 IP地址和 TEID信息。
1203、基站向所述移动管理实体发送初始化上下文响应或附着完成 消息, 完成公共路径的建立, 其中所述初始化上下文响应或附着完成消 息携带所述基站的网络地址和隧道端点标识符信息。
举例而言, MME接收该初始化上下文响应或附着完成消息后, 向 S-GW发送承载修改请求消息, 所述承载修改请求消息携带 eNB的 IP 地址和 TEID信息。 S-GW接收该承载修改请求消息后, 记录该 eNB的 IP地址和 TEID信息 , S-GW向 MME发送 载爹改响应消息。
本实施例提供的无线通信网络中公共路径的建立方法,通过基站向 移动管理实体发送附着请求,接收所述移动管理实体发送的携带服务网 关的网络地址和隧道端, *、标识符信 , 的初始化上下文请求或附着接受 消息,向所述移动管理实体发送携带所述基站的网络地址和隧道端点标 识符信息的初始化上下文响应或附着完成消息, 完成公共路径的建立。 因此, 同一组的 MTC Device与 MTC Server进行数据传输时, 公共路 径部分仅涉及一次建立承载的操作, 减少了节点之间的信令传输,从而 能够减少 M2M通信时所占用的网络资源, 提高 M2M网络业务的处理 效率。
另外,本发明实施例还提供了一种无线通信网络中单向上行公共路 径的使用方法, 如图 13所示, 包括:
1301、 基站接收机器设备发送的无线资源控制连接请求消息; 在本实施例中, 使用的公共路径为单向上行公共路径, 包括基站- 服务网关之间的上行路径, 基站-服务网关-分组数据网络网关之间的上 行路径, 或者基站 -服务网关-分组数据网络网关-机器服务器之间的上
行路径; 或者, 所述公共路径为双向公共路径, 包括基站 -服务网关之 间的双向路径, 基站-服务网关-分组数据网络网关之间的双向路径, 或 者基站-服务网关-分组数据网络网关-机器服务器之间的双向路径。
1302、 基站向所述机器设备发送无线资源控制连接建立消息;
1303、基站接收所述机器设备发送的无线资源控制连接建立完成消 息, 所述无线资源控制连接建立完成消息携带公共路径关联标识;
1304、基站根据所述公共路径相关联标识确定与所述机器设备对应 的公共路径;
举例而言,基站可以根据所述公共路径相关联标识确定与所述机器 设备对应的单向上行公共路径。或者,基站也可以根据所述公共路径相 关联标识确定与所述机器设备对应的双向公共路径。
1305、基站在接收机器设备发送的上行数据时, 通过所述公共路径 向所述公共路径的对端节点发送所述上行数据。
举例而言,基站可以在接收机器设备发送的上行数据时, 通过所述 单向上行公共路径向所述单向上行公共路径的对端节点发送所述上行 数据。 或者, 基站也可以在接收机器设备发送的上行数据时, 通过所述 双向公共路径向所述双向公共路径的对端节点发送所述上行数据。
另外 ,基站还可以在通过所述双向公共路径从所述双向公共路径的 对端节点接收下行数据时,根据所述下行数据中的设备标识确定对应的 机器设备, 向确定的机器设备发送所述下行数据。
本实施例提供的无线通信网络中公共路径的使用方法,通过基站接 收机器设备发送的无线资源控制连接请求消息,向所述机器设备发送无 线资源控制连接建立消息,接收所述机器设备发送的携带公共路径关联 标识的无线资源控制连接建立完成消息 ,根据所述公共路径相关联标识 确定与所述机器设备对应的公共路径,并在接收机器设备发送的上行数 据时, 通过所述公共路径向所述公共路径的对端节点发送所述上行数 据。 。 因此, 同一组的 MTC Device与 MTC Server进行数据传输时, 公共路径部分仅涉及一次建立承载的操作, 减少了节点之间的信令传 输, 从而能够减少 M2M通信时所占用的网络资源, 提高 M2M网络业 务的处理效率。
与上述方法相对应地, 本发明实施例还提供了一种 M2M的通信系 统, 如图 14所示, 包括:
网络单元 1401 , 用于获取与同路传输组的机器设备对应的公共路 径的特征信息; 根据所述特征信息建立所述公共路径; 在所述同路传输 组的机器设备与机器服务器 1402之间的数据传输结束时, 释放所述公 共路径;
机器服务器 1402 , 用于通过与所述同路传输组的机器设备对应的 公共路径, 与所述同路传输组的机器设备进行数据传输。
进一步地, 所述网络单元 1401 , 具体用于根据所述特征信息确定 所述公共路径的首节点和末节点以及所述公共路径的数据传输方向;在 所述首节点和末节点之间建立隧道; 并且, 在所述数据传输方向为上行 时 ,所述隧道的节点中存储所述节点的上一级节点的网络地址和接口信 息; 在所述数据传输方向为下行时, 所述隧道的节点中存储所述节点的 下一级节点的网络地址和接口信息; 在所述数据传输方向为上下行时, 所述隧道的节点中存储所述节点的上一级节点和下一级节点的网络地 址和接口信息。
进一步地, 所述网络单元 1401 , 还具体用于为所述同路传输组的 机器设备建立无线承载;基站中设定建立的无线承载与公共路径的对应 关系;在所述同路传输组的机器设备通过建立的无线承载发送上行数据 时,基站根据设定的无线承载与公共路径的对应关系确定对应的公共路 径, 将所述上行数据通过确定的公共路径发送给机器服务器。
进一步地, 所述网络单元 1401 , 还具体用于为所述同路传输组的 机器设备建立无线承载;基站中设定建立的无线承载与所述公共路径的 对应关系, 并设定机器设备信息与无线承载的对应关系; 在机器服务器 通过所述公共路径发送下行数据时,基站根据所述下行数据中的机器设 备信息以及设定的机器设备信息与无线承载的对应关系确定对应的无 线承载;基站通过确定的无线承载将所述下行数据发送给对应的机器设 备。
进一步地, 所述网络单元 1401 , 还具体用于为所述同路传输组的 机器设备建立无线承载, 并为所述同路传输组的机器设备分配网络地 址;基站中设定建立的无线承载与所述公共路径的对应关系, 并设定机 器设备的网络地址与无线承载的对应关系;在机器服务器通过所述公共 路径发送下行数据时,基站根据所述下行数据中的网络地址以及设定的 机器设备的网络地址与无线承载的对应关系确定对应的无线承载;基站
通过确定的无线承载将所述下行数据发送给对应的机器设备。
本发明实施例提供的 M2M的通信系统, 通过获取与同路传输组的 机器设备对应的公共路径的特征信息,根据所述特征信息建立所述公共 路径,同路传输组的机器设备通过所述公共路径与机器服务器进行数据 传输,并且在同路传输组的机器设备与机器服务器之间的数据传输结束 时释放所述公共路径。 因此, 同一组的 MTC Device与 MTC Server进 行数据传输时, 公共路径部分仅涉及一次建立承载和释放承载的操作, 减少了节点之间的信令传输, 从而能够减少 M2M通信时所占用的网络 资源, 提高 M2M网络业务的处理效率。
另外,本发明实施例还提供了一种无线通信网络中公共路径的建立 系统, 如图 15所示, 包括:
移动管理实体 1501 ,用于向服务网关 1502发送会话建立请求消息; 接收所述服务网关 1502发送的会话建立响应消息;向基站 1503发送承 载建立请求消息, 所述承载建立请求消息携带所述服务网关 1502的网 络地址和隧道端点标识符信息; 接收所述基站 1503发送的承载建立请 求响应完成公共路径的建立;
服务网关 1502 , 用于接收所述移动管理实体 1501发送的会话建立 请求消息; 向所述移动管理实体 1501发送会话建立响应消息, 所述会 话建立响应消息携带所述服务网关 1502的网络地址和隧道端点标识符 信息;
基站 1503 , 用于接收所述移动管理实体 1501发送的承载建立请求 消息; 向所述移动管理实体 1501发送承载建立响应消息。
进一步地, 所述移动管理实体 1501 , 具体用于当满足公共路径建 立触发条件时向服务网关 1502发送会话建立请求消息, 其中所述公共 路径建立触发条件包括预先设置的配置条件,预先设置的启动时间, 或 者网管 /维护系统下发的操作指令。
其中, 所述公共路径包括基站-服务网关之间的路径, 基站-服务网 关 -分组数据网络网关之间的路径, 或者基站 -服务网关-分组数据网络 网关-机器服务器之间的路径。 所述公共路径为单向上行路径或双向路 径。
本实施例提供的无线通信网络中公共路径的建立系统,通过移动管 理实体向服务网关发送会话建立请求消息,并接收所述服务网关发送的
携带所述服务网关的网络地址和隧道端点标识符信息的会话建立响应 消息,向基站发送携带所述服务网关的网络地址和隧道端点标识符信息 的承载建立请求消息,并接收所述基站发送的承载建立请求响应完成公 共路径的建立。 因此, 同一组的 MTC Device与 MTC Server进行数据 传输时,公共路径部分仅涉及一次建立承载的操作, 减少了节点之间的 信令传输, 从而能够减少 M2M通信时所占用的网络资源, 提高 M2M 网络业务的处理效率。
另外,本发明实施例还提供了一种无线通信网络中公共路径的建立 系统, 如图 16所示, 包括:
基站 1601 , 用于向移动管理实体 1602发送附着请求; 接收所述移 动管理实体 1602发送的初始化上下文请求或附着接受消息; 向所述移 动管理实体 1602发送初始化上下文响应或附着完成消息, 完成公共路 径的建立, 其中所述初始化上下文响应或附着完成消息携带所述基站 1601的网络地址和隧道端点标识符信息;
移动管理实体 1602 , 用于接收所述基站 1601发送的附着请求; 获 取服务网关的网络地址和隧道端点标识符信息; 向所述基站 1601发送 初始化上下文请求或附着接受消息,所述初始化上下文请求或附着接受 消息携带所述服务网关的网络地址和隧道端点标识符信息;接收所述基 站 1601发送的初始化上下文响应或附着完成消息。
进一步地, 基站 1601 , 具体用于在满足公共路径建立触发条件时, 向移动管理实体 1602发送附着请求, 所述公共路径建立触发条件包括 预先设置的配置条件, 预先设置的启动时间, 或者网管 /维护系统下发 的操作指令。
其中, 所述公共路径包括基站-服务网关之间的路径, 基站-服务网 关 -分组数据网络网关之间的路径, 或者基站 -服务网关-分组数据网络 网关-机器服务器之间的路径。 所述公共路径为单向上行路径或双向路 径。
本实施例提供的无线通信网络中公共路径的建立系统,通过基站向 移动管理实体发送附着请求,接收所述移动管理实体发送的携带服务网 关的网络地址和隧道端, *、标识符信 , 的初始化上下文请求或附着接受 消息,向所述移动管理实体发送携带所述基站的网络地址和隧道端点标 识符信息的初始化上下文响应或附着完成消息, 完成公共路径的建立。
因此, 同一组的 MTC Device与 MTC Server进行数据传输时, 公共路 径部分仅涉及一次建立承载的操作, 减少了节点之间的信令传输,从而 能够减少 M2M通信时所占用的网络资源, 提高 M2M网络业务的处理 效率。
另外,本发明实施例还提供了一种无线通信网络中公共路径的使用 系统, 如图 17所示, 包括:
机器设备 1701 ,用于向基站 1702发送无线资源控制连接请求消息; 接收所述基站 1702 发送的无线资源控制连接建立消息; 向所述基站 1702 发送无线资源控制连接建立完成消息, 所述无线资源控制连接建 立完成消息携带公共路径关联标识;
基站 1702 , 用于接收机器设备 1701发送的无线资源控制连接请求 消息; 向所述机器设备 1701发送无线资源控制连接建立消息; 接收所 述机器设备 1701发送的无线资源控制连接建立完成消息; 根据所述无 线资源控制连接建立完成消息中的公共路径相关联标识确定与所述机 器设备 1701对应的公共路径;在接收机器设备 1701发送的上行数据时, 通过所述公共路径向所述公共路径的对端节点发送所述上行数据。
进一步地, 所述基站 1702 , 具体用于根据所述公共路径相关联标 识确定与所述机器设备 1701对应的单向上行公共路径; 在接收机器设 备 1701发送的上行数据时, 通过所述单向上行公共路径向所述单向上 行公共路径的对端节点发送所述上行数据。
或者, 所述基站 1702 , 具体用于根据所述公共路径相关联标识确 定与所述机器设备 1701 对应的双向公共路径; 在接收机器设备 1701 发送的上行数据时 ,通过所述双向公共路径向所述双向公共路径的对端 节点发送所述上行数据。
进一步地, 所述基站 1702 , 还用于在通过所述双向公共路径从所 述双向公共路径的对端节点接收下行数据时,根据所述下行数据中的设 备标识确定对应的机器设备 1701 , 向确定的机器设备 1701发送所述下 行数据。
在本实施例中, 所述公共路径为单向上行公共路径, 包括基站-服 务网关之间的上行路径, 基站-服务网关-分组数据网络网关之间的上行 路径, 或者基站-服务网关-分组数据网络网关-机器服务器之间的上行 路径; 或者, 所述公共路径为双向公共路径, 包括基站-服务网关之间
的双向路径, 基站-服务网关-分组数据网络网关之间的双向路径, 或者 基站 -服务网关-分组数据网络网关-机器服务器之间的双向路径。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部 分流程,是可以通过计算机程序来指令相关的硬件来完成, 所述的程序 可存储于一计算机可读取存储介质中, 该程序在执行时, 可包括如上述 各方法的实施例的流程。 其中, 所述的存储介质可为磁碟、 光盘、 只读 存储记忆体 ( Read-Only Memory, ROM ) 或随机存储记忆体(Random
Access Memory, RAM ) 等。
以上所述, 仅为本发明的具体实施方式, 但本发明的保护范围并不 局限于此,任何熟悉本技术领域的技术人员在本发明揭露的技术范围内, 可轻易想到变化或替换, 都应涵盖在本发明的保护范围之内。 因此, 本 发明的保护范围应所述以权利要求的保护范围为准。
Claims
1、 一种无线通信网络中公共路径的建立方法, 其特征在于, 包括: 移动管理实体向服务网关发送会话建立请求消息;
接收所述服务网关发送的会话建立响应消息, 所述会话建立响应消 息是对所述会话建立请求消息的响应并携带所述服务网关的网络地址和 隧道端点标识符信息;
向基站发送承载建立请求消息, 所述承载建立请求消息携带所述服 务网关的网络地址和隧道端点标识符信息;
接收所述基站发送的承载建立请求响应完成公共路径的建立。
2、 根据权利要求 1所述的无线通信网络中公共路径的建立方法, 其 特征在于, 当满足公共路径建立触发条件时移动管理实体向服务网关发 送会话建立请求消息, 其中所述公共路径建立触发条件包括预先设置的 配置条件, 预先设置的启动时间, 或者网管 /维护系统下发的操作指令。
3、 根据权利要求 1所述的无线通信网络中公共路径的建立方法, 其 特征在于, 所述公共路径包括基站-服务网关之间的路径, 基站-服务网关 -分组数据网络网关之间的路径, 或者基站-服务网关-分组数据网络网关- 机器服务器之间的路径。
4、 根据权利要求 1所述的无线通信网络中公共路径的建立方法, 其 特征在于, 所述公共路径为单向上行路径或双向路径。
5、 一种无线通信网络中公共路径的建立方法, 其特征在于, 包括: 基站向移动管理实体发送附着请求;
接收所述移动管理实体发送的初始化上下文请求或附着接受消息, 所述初始化上下文请求或附着接受消息是对所述附着请求的响应并携带 服务网关的网络地址和隧道端点标识符信息;
向所述移动管理实体发送初始化上下文响应或附着完成消息, 完成 公共路径的建立, 其中所述初始化上下文响应或附着完成消息携带所述 基站的网络地址和隧道端点标识符信息。
6、 根据权利要求 5所述的无线通信网络中公共路径的建立方法, 其 特征在于, 基站在满足公共路径建立触发条件时, 向移动管理实体发送 附着请求, 所述公共路径建立触发条件包括预先设置的配置条件, 预先 设置的启动时间, 或者网管 /维护系统下发的操作指令。
7、 根据权利要求 5所述的无线通信网络中公共路径的建立方法, 其 特征在于, 所述公共路径包括基站-服务网关之间的路径, 基站-服务网关 -分组数据网络网关之间的路径, 或者基站-服务网关-分组数据网络网关- 机器服务器之间的路径。
8、 根据权利要求 5所述的无线通信网络中公共路径的建立方法, 其 特征在于, 所述公共路径为单向上行路径或双向路径。
9、一种无线通信网络中单向上行公共路径的使用方法,其特征在于, 包括:
基站接收机器设备发送的无线资源控制连接请求消息;
向所述机器设备发送无线资源控制连接建立消息;
接收所述机器设备发送的无线资源控制连接建立完成消息, 所述无 线资源控制连接建立完成消息携带公共路径关联标识;
根据所述公共路径相关联标识确定与所述机器设备对应的公共路 径;
在接收机器设备发送的上行数据时, 通过所述公共路径向所述公共 路径的对端节点发送所述上行数据。
10、 根据权利要求 9 所述的方法, 其特征在于, 所述根据所述公共 路径相关联标识确定与所述机器设备对应的公共路径包括: 根据所述公 共路径相关联标识确定与所述机器设备对应的单向上行公共路径;
在接收机器设备发送的上行数据时, 通过所述公共路径向所述公共 路径的对端节点发送所述上行数据包括:
在接收机器设备发送的上行数据时, 通过所述单向上行公共路径向 所述单向上行公共路径的对端节点发送所述上行数据。
1 1、 根据权利要求 9 所述的方法, 其特征在于, 所述根据所述公共 路径相关联标识确定与所述机器设备对应的公共路径包括: 根据所述公 共路径相关联标识确定与所述机器设备对应的双向公共路径;
在接收机器设备发送的上行数据时, 通过所述公共路径向所述公共 路径的对端节点发送所述上行数据包括:
在接收机器设备发送的上行数据时, 通过所述双向公共路径向所述 双向公共路径的对端节点发送所述上行数据。
12、 根据权利要求 1 1所述的方法, 其特征在于, 所述方法还包括 在通过所述双向公共路径从所述双向公共路径的对端节点接收下行 数据时, 根据所述下行数据中的设备标识确定对应的机器设备, 向确定 的机器设备发送所述下行数据。
13、 根据权利要求所述的无线通信网络中单向上行公共路径的使用 方法, 其特征在于, 所述公共路径为单向上行公共路径, 包括基站 -服务 网关之间的上行路径, 基站-服务网关-分组数据网络网关之间的上行路 径, 或者基站-服务网关-分组数据网络网关-机器服务器之间的上行路径; 或者
所述公共路径为双向公共路径,包括基站-服务网关之间的双向路径, 基站 -服务网关-分组数据网络网关之间的双向路径, 或者基站-服务网关- 分组数据网络网关-机器服务器之间的双向路径。
14、 一种 M2M的通信方法, 其特征在于, 包括:
获取与同路传输组的机器设备对应的公共路径的特征信息;
根据所述特征信息建立所述公共路径;
所述同路传输组的机器设备通过所述公共路径与机器服务器进行数 据传输;
在所述同路传输组的机器设备与所述机器服务器之间的数据传输结 束时, 译放所述公共路径。
15、 根据权利要求 14所述的 M2M的通信方法, 其特征在于, 所述 根据所述特征信息建立所述公共路径包括:
根据所述特征信息确定所述公共路径的首节点和末节点以及所述公 共路径的数据传输方向;
在所述首节点和末节点之间建立隧道; 并且, 在所述数据传输方向 为上行时, 所述隧道的节点中存储所述节点的上一级节点的网络地址和 接口信息; 在所述数据传输方向为下行时, 所述隧道的节点中存储所述 节点的下一级节点的网络地址和接口信息; 在所述数据传输方向为上下 行时, 所述隧道的节点中存储所述节点的上一级节点和下一级节点的网 络地址和接口信息。
16、 根据权利要求 14所述的 M2M的通信方法, 其特征在于, 所述 同路传输组的机器设备通过所述公共路径与机器服务器进行数据传输包 括:
为所述同路传输组的机器设备建立无线承载;
基站中设定建立的无线承载与公共路径的对应关系;
在所述同路传输组的机器设备通过建立的无线承载发送上行数据 时, 基站根据设定的无线承载与公共路径的对应关系确定对应的公共路 径, 将所述上行数据通过确定的公共路径发送给机器服务器。
17、 根据权利要求 16所述的 Μ2Μ的通信方法, 其特征在于, 所述 在所述同路传输组的机器设备通过建立的无线承载发送上行数据时, 基 站根据设定的无线承载与公共路径的对应关系确定对应的公共路径, 将 所述上行数据通过确定的公共路径发送给机器服务器包括:
在所述同路传输组的机器设备通过建立的无线承载发送上行数据 时, 基站根据设定的无线承载与公共路径的对应关系确定对应的公共路 径, 将所述上行数据通过所述公共路径发送给分组数据网络网关;
所述分组数据网络网关根据所述上行数据中的网络地址将所述上行 数据发送给机器服务器。
18、根据权利要求 14-17任一所述的 Μ2Μ的通信方法,其特征在于, 所述同路传输组的机器设备通过所述公共路径与机器服务器进行数据传 输包括:
为所述同路传输组的机器设备建立无线承载;
基站中设定建立的无线承载与所述公共路径的对应关系, 并设定机 器设备信息与无线承载的对应关系;
在机器服务器通过所述公共路径发送下行数据时, 基站根据所述下 行数据中的机器设备信息以及设定的机器设备信息与无线承载的对应关 系确定对应的无线承载;
基站通过确定的无线承载将所述下行数据发送给对应的机器设备。
19、根据权利要求 14-17任一所述的 Μ2Μ的通信方法,其特征在于, 所述同路传输组的机器设备通过所述公共路径与机器服务器进行数据传 输包括:
为所述同路传输组的机器设备建立无线承载, 并为所述同路传输组 的机器设备分配网络地址;
基站中设定建立的无线承载与所述公共路径的对应关系, 并设定机 器设备的网络地址与无线承载的对应关系;
在机器服务器通过所述公共路径发送下行数据时, 基站根据所述下 行数据中的网络地址以及设定的机器设备的网络地址与无线承载的对应 关系确定对应的无线承载;
基站通过确定的无线承载将所述下行数据发送给对应的机器设备。
20、 一种无线通信网络中公共路径的建立系统, 其特征在于, 包括: 移动管理实体, 用于向服务网关发送会话建立请求消息; 接收所述 服务网关发送的会话建立响应消息; 向基站发送承载建立请求消息, 所 述承载建立请求消息携带所述服务网关的网络地址和隧道端点标识符信 息; 接收所述基站发送的承载建立请求响应完成公共路径的建立;
服务网关, 用于接收所述移动管理实体发送的会话建立请求消息; 向所述移动管理实体发送会话建立响应消息, 所述会话建立响应消息携 带所述服务网关的网络地址和隧道端点标识符信息;
基站, 用于接收所述移动管理实体发送的承载建立请求消息; 向所 述移动管理实体发送承载建立响应消息。
21、 根据权利要求 20所述的系统, 其特征在于, 所述移动管理实体, 具体用于当满足公共路径建立触发条件时向服务网关发送会话建立请求 消息, 其中所述公共路径建立触发条件包括预先设置的配置条件, 预先 设置的启动时间, 或者网管 /维护系统下发的操作指令。
22、 根据权利要求 20所述的系统, 其特征在于, 所述公共路径包括 基站 -服务网关之间的路径, 基站 -服务网关-分组数据网络网关之间的路 径, 或者基站-服务网关 -分组数据网络网关 -机器服务器之间的路径。
23、 根据权利要求 20所述的系统, 其特征在于, 所述公共路径为单 向上行路径或双向路径。
24、 一种无线通信网络中公共路径的建立系统, 其特征在于, 包括: 基站, 用于向移动管理实体发送附着请求; 接收所述移动管理实体 发送的初始化上下文请求或附着接受消息; 向所述移动管理实体发送初 始化上下文响应或附着完成消息, 完成公共路径的建立, 其中所述初始 化上下文响应或附着完成消息携带所述基站的网络地址和隧道端点标识 符信息;
移动管理实体, 用于接收所述基站发送的附着请求; 获取服务网关 的网络地址和隧道端点标识符信息; 向所述基站发送初始化上下文请求 或附着接受消息, 所述初始化上下文请求或附着接受消息携带所述服务 网关的网络地址和隧道端点标识符信息; 接收所述基站发送的初始化上 下文响应或附着完成消息。
25、 根据权利要求 24所述的系统, 其特征在于, 基站, 具体用于在 满足公共路径建立触发条件时, 向移动管理实体发送附着请求, 所述公 共路径建立触发条件包括预先设置的配置条件, 预先设置的启动时间, 或者网管 /维护系统下发的操作指令。
26、 根据权利要求 24所述的系统, 其特征在于, 所述公共路径包括 基站-服务网关之间的路径, 基站-服务网关-分组数据网络网关之间的路 径, 或者基站-服务网关 -分组数据网络网关 -机器服务器之间的路径。
27、 根据权利要求 24所述的系统, 其特征在于, 所述公共路径为单 向上行路径或双向路径。
28、 一种无线通信网络中单向上行公共路径的使用系统, 其特征在 于, 包括:
机器设备, 用于向基站发送无线资源控制连接请求消息; 接收所述 基站发送的无线资源控制连接建立消息; 向所述基站发送无线资源控制 连接建立完成消息, 所述无线资源控制连接建立完成消息携带公共路径 关联标识;
基站, 用于接收机器设备发送的无线资源控制连接请求消息; 向所 述机器设备发送无线资源控制连接建立消息; 接收所述机器设备发送的 无线资源控制连接建立完成消息; 根据所述无线资源控制连接建立完成 消息中的公共路径相关联标识确定与所述机器设备对应的公共路径; 在 接收机器设备发送的上行数据时, 通过所述公共路径向所述公共路径的 对端节点发送所述上行数据。
29、 根据权利要求 28所述的系统, 其特征在于, 所述基站, 具体用 于根据所述公共路径相关联标识确定与所述机器设备对应的单向上行公 共路径; 在接收机器设备发送的上行数据时, 通过所述单向上行公共路 径向所述单向上行公共路径的对端节点发送所述上行数据。
30、 根据权利要求 29所述的系统, 其特征在于, 所述基站, 具体用 于根据所述公共路径相关联标识确定与所述机器设备对应的双向公共路 径; 在接收机器设备发送的上行数据时, 通过所述双向公共路径向所述 双向公共路径的对端节点发送所述上行数据。
31、 根据权利要求 29所述的系统, 其特征在于, 所述基站, 还用于 在通过所述双向公共路径从所述双向公共路径的对端节点接收下行数据 时, 根据所述下行数据中的设备标识确定对应的机器设备, 向确定的机 器设备发送所述下行数据。
32、 根据权利要求 29所述的系统, 其特征在于, 所述公共路径为单 向上行公共路径, 包括基站-服务网关之间的上行路径, 基站-服务网关- 分组数据网络网关之间的上行路径, 或者基站-服务网关-分组数据网络网 关-机器服务器之间的上行路径; 或者
所述公共路径为双向公共路径,包括基站-服务网关之间的双向路径, 基站 -服务网关-分组数据网络网关之间的双向路径, 或者基站-服务网关- 分组数据网络网关-机器服务器之间的双向路径。
33、 一种 M2M的通信系统, 其特征在于, 包括:
网络单元, 用于获取与同路传输组的机器设备对应的公共路径的特 征信息; 根据所述特征信息建立所述公共路径; 在所述同路传输组的机 器设备与机器服务器之间的数据传输结束时, 释放所述公共路径;
机器服务器, 用于通过与所述同路传输组的机器设备对应的公共路 径, 与所述同路传输组的机器设备进行数据传输。
34、 根据权利要求 33所述的 M2M的通信系统, 其特征在于, 所述 网络单元, 用于根据所述特征信息确定所述公共路径的首节点和末节点 以及所述公共路径的数据传输方向; 在所述首节点和末节点之间建立隧 道; 并且, 在所述数据传输方向为上行时, 所述隧道的节点中存储所述 节点的上一级节点的网络地址和接口信息; 在所述数据传输方向为下行 时, 所述隧道的节点中存储所述节点的下一级节点的网络地址和接口信 息; 在所述数据传输方向为上下行时, 所述隧道的节点中存储所述节点 的上一级节点和下一级节点的网络地址和接口信息。
35、 根据权利要求 33所述的 M2M的通信系统, 其特征在于, 所述 网络单元, 还用于为所述同路传输组的机器设备建立无线承载; 基站中 设定建立的无线承载与公共路径的对应关系; 在所述同路传输组的机器 设备通过建立的无线承载发送上行数据时, 基站根据设定的无线承载与 公共路径的对应关系确定对应的公共路径, 将所述上行数据通过确定的 公共路径发送给机器服务器。
36、根据权利要求 33-35任一所述的 M2M的通信系统,其特征在于, 所述网络单元, 还用于为所述同路传输组的机器设备建立无线承载; 基 站中设定建立的无线承载与所述公共路径的对应关系, 并设定机器设备 信息与无线承载的对应关系; 在机器服务器通过所述公共路径发送下行 数据时, 基站根据所述下行数据中的机器设备信, 以及设定的机器设备 信息与无线承载的对应关系确定对应的无线承载; 基站通过确定的无线 承载将所述下行数据发送给对应的机器设备。
37、根据权利要求 33-35任一所述的 M2M的通信系统,其特征在于, 所述网络单元, 还用于为所述同路传输组的机器设备建立无线承载, 并 为所述同路传输组的机器设备分配网络地址; 基站中设定建立的无线承 载与所述公共路径的对应关系, 并设定机器设备的网络地址与无线承载 的对应关系; 在机器服务器通过所述公共路径发送下行数据时, 基站根 据所述下行数据中的网络地址以及设定的机器设备的网络地址与无线承 载的对应关系确定对应的无线承载; 基站通过确定的无线承载将所述下 行数据发送给对应的机器设备。
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP11849038.2A EP2642815A4 (en) | 2010-12-15 | 2011-12-15 | METHOD FOR ESTABLISHING AND USING A PUBLIC PATH, AND METHOD AND SYSTEM FOR M2M COMMUNICATION |
EP14188474.2A EP2846600B1 (en) | 2010-12-15 | 2011-12-15 | M2M communication method and system thereof |
US13/915,331 US9173244B2 (en) | 2010-12-15 | 2013-06-11 | Methods for establishing and using public path, M2M communication method, and systems thereof |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201010590124.1A CN102548019B (zh) | 2010-12-15 | 2010-12-15 | 公共路径的建立和使用方法、m2m的通信方法及系统 |
CN201010590124.1 | 2010-12-15 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/915,331 Continuation US9173244B2 (en) | 2010-12-15 | 2013-06-11 | Methods for establishing and using public path, M2M communication method, and systems thereof |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2012079527A1 true WO2012079527A1 (zh) | 2012-06-21 |
Family
ID=46244116
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2011/084073 WO2012079527A1 (zh) | 2010-12-15 | 2011-12-15 | 公共路径的建立和使用方法、m2m的通信方法及系统 |
Country Status (4)
Country | Link |
---|---|
US (1) | US9173244B2 (zh) |
EP (2) | EP2846600B1 (zh) |
CN (1) | CN102548019B (zh) |
WO (1) | WO2012079527A1 (zh) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2014107902A1 (zh) * | 2013-01-14 | 2014-07-17 | 华为技术有限公司 | 用户设备的注册方法、近距离业务服务器和移动管理实体 |
Families Citing this family (23)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20130013741A1 (en) * | 2011-07-04 | 2013-01-10 | Nederlandse Organisatie Voor Toegepast-Natuurwetenschappelijk Onderzoek Tno | Triggering With Time Indicator |
EP3425850B1 (en) * | 2012-08-01 | 2020-10-28 | Huawei Technologies Co., Ltd. | Method and device for processing communication path |
CN110213032B (zh) * | 2012-12-18 | 2021-10-08 | 北京三星通信技术研究有限公司 | 配置ue的聚合最大速率的方法 |
CN104350771A (zh) * | 2013-05-09 | 2015-02-11 | 华为技术有限公司 | 网络配置的方法和装置 |
US9596628B2 (en) | 2013-10-31 | 2017-03-14 | Intel Corporation | Gateway arrangements for wireless communication networks |
KR20150095507A (ko) * | 2014-02-13 | 2015-08-21 | 한국전자통신연구원 | 머신 타입 통신 단말의 인터넷 프로토콜 주소 할당 방법 및 장치 |
CN105430766A (zh) * | 2014-09-23 | 2016-03-23 | 中兴通讯股份有限公司 | 一种mtc业务处理方法、系统及mtc设备 |
KR102476574B1 (ko) * | 2015-07-31 | 2022-12-09 | 인텔 코포레이션 | 비 ip 기반 eps 베어러를 사용하는 장치, 시스템 및 방법 |
US10972552B2 (en) * | 2016-09-30 | 2021-04-06 | Huawei Technologies Co., Ltd. | Method and system for user plane path selection |
US10405158B2 (en) | 2017-02-27 | 2019-09-03 | Oracle International Corporation | Methods, systems and computer readable media for providing service capability exposure function (SCEF) as a diameter routing agent (DRA) feature |
US10530599B2 (en) | 2017-02-27 | 2020-01-07 | Oracle International Corporation | Methods, systems and computer readable media for providing service capability exposure function (SCEF) as a cloud service |
US10506403B2 (en) | 2017-02-27 | 2019-12-10 | Oracle International Corporation | Methods, systems and computer readable media for providing integrated service capability exposure function (SCEF), service capability server (SCS) and application server (AS) services |
US10448449B2 (en) | 2017-07-13 | 2019-10-15 | Oracle International Corporation | Methods, systems, and computer readable media for dynamically provisioning session timeout information in a communications network |
US10334419B2 (en) * | 2017-08-16 | 2019-06-25 | Oracle International Corporation | Methods, systems, and computer readable media for optimizing machine type communication (MTC) device signaling |
US10313883B2 (en) | 2017-11-06 | 2019-06-04 | Oracle International Corporation | Methods, systems, and computer readable media for using authentication validation time periods |
US11153920B2 (en) | 2017-12-15 | 2021-10-19 | Hewlett Packard Enterprise Development Lp | Establishing a GTP session |
US11233856B2 (en) | 2017-12-15 | 2022-01-25 | Hewlett Packard Enterprise Development Lp | Selecting an address of a device |
US11025541B2 (en) * | 2017-12-15 | 2021-06-01 | Hewlett Packard Enterprises Development LP | Transporting a GTP message to a termination device |
US11146577B2 (en) | 2018-05-25 | 2021-10-12 | Oracle International Corporation | Methods, systems, and computer readable media for detecting and mitigating effects of abnormal behavior of a machine type communication (MTC) device |
US10616802B2 (en) | 2018-09-04 | 2020-04-07 | Oracle International Corporation | Methods, systems and computer readable media for overload and flow control at a service capability exposure function (SCEF) |
US11516263B2 (en) * | 2019-03-14 | 2022-11-29 | T-Mobile Usa, Inc. | Secure and transparent transport of application level protocols to non-IP data delivery communication channels |
US11381955B2 (en) | 2020-07-17 | 2022-07-05 | Oracle International Corporation | Methods, systems, and computer readable media for monitoring machine type communications (MTC) device related information |
US11700510B2 (en) | 2021-02-12 | 2023-07-11 | Oracle International Corporation | Methods, systems, and computer readable media for short message delivery status report validation |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101176330A (zh) * | 2005-03-24 | 2008-05-07 | 奥林奇股份有限公司 | 激活分组数据协议上下文的方法和系统 |
US20090217038A1 (en) * | 2008-02-22 | 2009-08-27 | Vesa Petteri Lehtovirta | Methods and Apparatus for Locating a Device Registration Server in a Wireless Network |
CN101588570A (zh) * | 2008-05-20 | 2009-11-25 | 华为技术有限公司 | 建立用户面单隧道的方法、系统及其基站子系统 |
CN101860807A (zh) * | 2010-05-05 | 2010-10-13 | 工业和信息化部电信传输研究所 | 一种m2m终端设备组的管理、建立通信方法及装置 |
Family Cites Families (16)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
ATE441304T1 (de) * | 2003-10-01 | 2009-09-15 | Actix Ltd | Anrufverfolgungssysteme |
CN1859374B (zh) | 2005-11-09 | 2010-05-12 | 华为技术有限公司 | 在一条永久虚连接上承载多种业务的方法 |
CN101409951B (zh) * | 2007-10-11 | 2010-08-25 | 华为技术有限公司 | 承载建立方法及相关装置 |
EP2294856A1 (en) * | 2008-06-19 | 2011-03-16 | Telefonaktiebolaget LM Ericsson (publ) | Transfer of connections triggered by a mme in case of failure of a serving gateway |
DE102008037725A1 (de) * | 2008-08-14 | 2010-02-18 | Deutsche Telekom Ag | Verfahren zur multiplen physikalischen Nutzung einer einzigen Identifikation in TK Netzen |
WO2010041622A1 (ja) * | 2008-10-06 | 2010-04-15 | 日本電気株式会社 | 通信システム、接続制御装置、移動端末、基地局制御方法、サービス要求方法、およびプログラム |
US9480092B2 (en) * | 2009-04-23 | 2016-10-25 | Qualcomm Incorporated | Establishing packet data network connectivity for local internet protocol access traffic |
KR101652442B1 (ko) * | 2009-05-05 | 2016-08-30 | 엘지전자 주식회사 | 이동통신 네트워크 내에서 제어 평면(Control Plane)을 담당하는 서버 및 커넥션 설정을 제어하는 방법 |
US8811961B2 (en) * | 2010-03-11 | 2014-08-19 | Lg Electronics Inc. | Method and apparatus for MTC in a wireless communication system |
US9215588B2 (en) * | 2010-04-30 | 2015-12-15 | Cisco Technology, Inc. | System and method for providing selective bearer security in a network environment |
US8438278B2 (en) * | 2010-05-03 | 2013-05-07 | Htc Corporation | Methods for monitoring and reporting MTC events |
US8942175B2 (en) * | 2010-05-04 | 2015-01-27 | Lg Electronics Inc. | Method for controlling MTC service network overload in mobile communication system and device thereof |
US20110310731A1 (en) * | 2010-06-18 | 2011-12-22 | Sharp Laboratories Of America, Inc. | Controlling network resource usage of machine type communication (mtc) devices |
US9749880B2 (en) * | 2010-06-30 | 2017-08-29 | Verizon Patent And Licensing Inc. | Base station failover using neighboring base stations as relays |
US20120033613A1 (en) * | 2010-08-04 | 2012-02-09 | National Taiwan University | Enhanced rach design for machine-type communications |
US20120044865A1 (en) * | 2010-08-20 | 2012-02-23 | Industrial Technology Research Institute | Apparatus And Method For Coupling An M2M Device To A Wireless Network |
-
2010
- 2010-12-15 CN CN201010590124.1A patent/CN102548019B/zh active Active
-
2011
- 2011-12-15 EP EP14188474.2A patent/EP2846600B1/en active Active
- 2011-12-15 EP EP11849038.2A patent/EP2642815A4/en not_active Withdrawn
- 2011-12-15 WO PCT/CN2011/084073 patent/WO2012079527A1/zh active Application Filing
-
2013
- 2013-06-11 US US13/915,331 patent/US9173244B2/en active Active
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101176330A (zh) * | 2005-03-24 | 2008-05-07 | 奥林奇股份有限公司 | 激活分组数据协议上下文的方法和系统 |
US20090217038A1 (en) * | 2008-02-22 | 2009-08-27 | Vesa Petteri Lehtovirta | Methods and Apparatus for Locating a Device Registration Server in a Wireless Network |
CN101588570A (zh) * | 2008-05-20 | 2009-11-25 | 华为技术有限公司 | 建立用户面单隧道的方法、系统及其基站子系统 |
CN101860807A (zh) * | 2010-05-05 | 2010-10-13 | 工业和信息化部电信传输研究所 | 一种m2m终端设备组的管理、建立通信方法及装置 |
Non-Patent Citations (1)
Title |
---|
See also references of EP2642815A4 * |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2014107902A1 (zh) * | 2013-01-14 | 2014-07-17 | 华为技术有限公司 | 用户设备的注册方法、近距离业务服务器和移动管理实体 |
Also Published As
Publication number | Publication date |
---|---|
EP2846600A2 (en) | 2015-03-11 |
EP2846600A3 (en) | 2015-07-22 |
US9173244B2 (en) | 2015-10-27 |
EP2642815A4 (en) | 2014-04-09 |
EP2846600B1 (en) | 2019-02-06 |
CN102548019A (zh) | 2012-07-04 |
CN102548019B (zh) | 2016-07-27 |
US20130272247A1 (en) | 2013-10-17 |
EP2642815A1 (en) | 2013-09-25 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2012079527A1 (zh) | 公共路径的建立和使用方法、m2m的通信方法及系统 | |
EP3518596B1 (en) | Communication method and access network device | |
CN110753335B (zh) | 信息传输方法、设备及计算机可读存储介质 | |
EP1881660B1 (en) | A method, apparatus and system for wireless access | |
WO2019214729A1 (zh) | 数据处理的方法和设备 | |
WO2019033920A1 (zh) | 网络侧对远端用户设备的识别和控制方法以及设备 | |
WO2013064104A1 (zh) | 一种数据传输方法、移动性管理实体和移动终端 | |
WO2013097641A1 (zh) | 实现集群业务的方法、实体及系统 | |
JP2018528684A (ja) | データ処理方法及びデバイス | |
KR20070073343A (ko) | 이동통신 ims시스템에서 아이들모드 단말기의 세션 설정프로토콜 데이터를 전송하는 방법 및 장치 | |
US9179443B2 (en) | Method and apparatus for providing services at terminal of mobile communication system | |
WO2011134329A1 (zh) | 一种小数据包传输的方法和系统 | |
WO2022001761A1 (zh) | 通信方法及装置 | |
WO2011018002A1 (zh) | 一种传输承载的中继方法、装置和通信系统 | |
US9992109B2 (en) | Data transmission method, apparatus and system | |
CN105359573B (zh) | 用于在无线通信系统中卸载数据业务的方法和装置 | |
WO2012130068A1 (zh) | 数据包传输方法和相关装置 | |
WO2015062287A1 (zh) | 终端的本地交换方法及系统 | |
WO2018082070A1 (zh) | 一种数据报文处理方法及控制面网元、用户面网元 | |
WO2013053376A1 (en) | A method of and apparatus for establishing bearer attributes | |
WO2019136925A1 (zh) | 一种数据传输方法及装置、计算机存储介质 | |
WO2017140234A1 (zh) | 一种diameter信令网关的实现方法、装置和系统 | |
WO2009076846A1 (zh) | 紧急服务呼叫的处理方法 | |
KR102170158B1 (ko) | 위치 기반 mbms 방송 서비스 제어 방법 및 장치 | |
WO2019136927A1 (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: 11849038 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2011849038 Country of ref document: EP |