WO2014181439A1 - Systeme de communication, dispositif terminal et procede de communication - Google Patents
Systeme de communication, dispositif terminal et procede de communication Download PDFInfo
- Publication number
- WO2014181439A1 WO2014181439A1 PCT/JP2013/063079 JP2013063079W WO2014181439A1 WO 2014181439 A1 WO2014181439 A1 WO 2014181439A1 JP 2013063079 W JP2013063079 W JP 2013063079W WO 2014181439 A1 WO2014181439 A1 WO 2014181439A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- base station
- information
- small data
- communication system
- terminal device
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Ceased
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
- H04W8/08—Mobility data transfer
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/02—Services making use of location information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W74/00—Wireless channel access
- H04W74/08—Non-scheduled access, e.g. ALOHA
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
- H04W8/06—Registration at serving network Location Register, VLR or user mobility server
Definitions
- the present invention relates to a communication system, a terminal device, and a communication method.
- MTC Machine Type Communication
- base station a base station device
- terminal device a terminal device
- MTC Machine Type Communication
- a smart meter having a wireless communication function transmits, for example, measured power consumption data to the base station.
- the vending machine having a wireless communication function transmits, for example, sales information, inventory information in the vending machine, and the like to the base station.
- GPS Global Positioning System
- the MTC terminal transmits / receives the specific data (information) as described above, compared to a general terminal (for example, a smartphone) that transmits / receives various types of data, the type of data desired as a communication target, And the amount of data is small. That is, in the MTC terminal, “small size user data” (hereinafter sometimes referred to as “small data”) such as measurement data is intermittently transmitted and received in relatively many cases.
- An object of the present invention is to provide a terminal device and a communication method.
- a terminal device that transmits user data to a base station in a random access procedure executed in response to occurrence of uplink user data is a network control device that transmits information on user data before starting the random access procedure.
- FIG. 1 is a diagram illustrating an example of a communication system according to the first embodiment.
- FIG. 2 is a block diagram illustrating an example of a terminal according to the first embodiment.
- FIG. 3 is a block diagram illustrating an example of the base station according to the first embodiment.
- FIG. 4 is a diagram illustrating an example of the MME according to the first embodiment.
- FIG. 5 is a sequence diagram illustrating an example of processing of the communication system according to the first embodiment.
- FIG. 6 is a sequence diagram illustrating an example of processing of the communication system according to the first embodiment.
- FIG. 7 is a sequence diagram illustrating an example of processing of the communication system according to the first embodiment.
- FIG. 8 is a sequence diagram illustrating an example of processing of the communication system according to the first embodiment.
- FIG. 1 is a diagram illustrating an example of a communication system according to the first embodiment.
- FIG. 2 is a block diagram illustrating an example of a terminal according to the first embodiment.
- FIG. 3 is a block
- FIG. 9 is a sequence diagram illustrating an example of processing of the communication system according to the first embodiment.
- FIG. 10 is a diagram illustrating a hardware configuration example of the terminal.
- FIG. 11 is a diagram illustrating a hardware configuration example of the base station.
- FIG. 12 is a diagram illustrating a hardware configuration example of the MME.
- FIG. 1 is a diagram illustrating an example of a communication system according to the first embodiment.
- the communication system 1 includes a terminal 10, a base station 20, an MME (Mobility Management Entity) 30, and an S-GW (Serving-Gateway) 40.
- the MME 30 is a network control device.
- a C-plane path for exchanging control messages is set among the base station 20, the MME 30, and the S-GW 40.
- a U-plane path through which user data is exchanged is set between the base station 20 and the S-GW 40.
- the terminal 10 is an MTC terminal, and therefore the data transmitted and received by the terminal 10 is small data. In this embodiment, the small data is transmitted together with the control message using C-plane instead of U-plane.
- FIG. 2 is a block diagram illustrating an example of a terminal according to the first embodiment.
- a terminal 10 that is an MTC terminal includes a transmission unit 11, an antenna 12, a reception unit 13, and a control information processing unit 14.
- the user data input to the control information processing unit 14 is small data.
- the control information processing unit 14 forms information related to the small data (hereinafter, sometimes referred to as “Information of Small Data”) and outputs the information to the transmission unit 11.
- the small data information is, for example, the maximum data size per one piece of small data, transmission priority, required QoS (Quality of Service), etc., and is information used for allocating communication resources for the small data.
- the control information processing unit 14 forms at least one of these pieces of information as small data information and outputs the small data information to the transmission unit 11. Further, the control information processing unit 14 forms various control messages and outputs them to the transmission unit 11.
- the formation of the control message in the control information processing unit 14 may be performed according to the control message input from the receiving unit 13.
- the control information processing unit 14 adds the small data information or the small data to the specific control message and outputs it to the transmission unit 11.
- the transmission unit 11 transmits the small data information, the control message, and the small data to the base station 20 via the antenna 12 in the uplink.
- the receiving unit 13 receives the control message transmitted from the base station 20 on the downlink via the antenna 12 and outputs the control message to the control information processing unit 14.
- FIG. 3 is a block diagram illustrating an example of the base station according to the first embodiment.
- the base station 20 includes an antenna 21, a reception unit 22, an eNB communication control unit 23, a network IF (interface) 24, a transmission unit 25, and a storage unit 26.
- the receiving unit 22 receives the small data information, the control message, and the small data transmitted from the terminal 10 on the uplink via the antenna 21 and outputs them to the eNB communication control unit 23.
- the eNB communication control unit 23 forms various control messages and outputs them to the transmission unit 25 or the network IF 24.
- the formation of the control message in the eNB communication control unit 23 may be performed according to a control message input from the reception unit 13 or a control message input from the network IF 24.
- the eNB communication control unit 23 stores the small data information in the storage unit 26 together with the identifier of the terminal 10.
- the eNB communication control part 23 allocates a communication resource with respect to small data using small data information. Further, the eNB communication control unit 23 outputs the small data information and the small data input from the reception unit 22 to the network IF 24.
- the storage unit 26 stores small data information in association with the identifier of each of the plurality of terminals 10.
- the transmission unit 25 transmits a control message input from the eNB communication control unit 23 to the terminal 10 via the antenna 21 on the downlink.
- the network IF 24 is connected to the MME 30 via a C-plane path, transmits small data information, control messages, and small data to the MME 30 and receives control messages from the MME 30.
- the network IF 24 is connected to the S-GW 40 via a U-plane path.
- FIG. 4 is a block diagram illustrating an example of the MME according to the first embodiment. 4, the MME 30 includes a network IF 31, an MME communication control unit 32, a storage unit 33, and a network IF 34.
- the network IF 31 is connected to the base station 20 through a C-plane path, receives small data information, control messages, and small data from the base station 20 and outputs them to the MME communication control unit 32. Further, the network IF 31 transmits a control message input from the MME communication control unit 32 to the base station 20.
- the MME communication control unit 32 forms various control messages and outputs them to the network IF 31 or the network IF 34.
- the formation of the control message in the MME communication control unit 32 may be performed according to a control message input from the network IF 31 or the network IF 34.
- the MME communication control unit 32 stores the small data information in the storage unit 33 together with the identifier of the terminal 10. Further, the MME communication control unit 32 outputs the small data input from the network IF 31 to the network IF 34.
- the storage unit 33 stores small data information in association with the identifier of each of the plurality of terminals 10.
- the network IF 34 is connected to the S-GW 40 via a C-plane path, transmits a control message and small data to the S-GW 40, and receives a control message from the S-GW 40.
- FIGS. 5 to 9 are sequence diagrams illustrating an example of processing of the communication system according to the first embodiment.
- the terminal 10 in the sequence examples 1 to 5 transmits the small data to the base station 20 in a random access procedure (hereinafter sometimes referred to as “small data RA procedure”) executed in response to the occurrence of uplink small data. Send.
- the small data RA procedure is executed every time small data is generated.
- Sequence example 1 is shown in FIG. FIG. 5 is a sequence executed before small data to be transmitted from the terminal 10 is generated. That is, the terminal 10 of this example notifies the MME 30 of the small data information in advance before starting the small data RA procedure. For example, the terminal 10 notifies the MME 30 of the small data information in the “attach procedure” executed before the start of the small data RA procedure.
- the “attach procedure” is a procedure including a process of making an attach request (Attach Request) to the network first after the terminal 10 is turned on. Further, since the attach procedure is executed before the small data RA procedure corresponding to the “second random access procedure”, the attach procedure corresponds to the “first random access procedure”. Note that the information exchanged in steps S52 to S58 in FIG. 5 corresponds to a control message.
- RRC Radio Resource Control
- Setup Setup
- small data information Information of Small Data
- S-TMSI S-TMSI
- the base station 20 transmits an Attach Request to the MME 30 and forms an Initial UE Message including S-TMSI and small data information and transmits the message to the MME 30.
- the MME 30 associates the S-TMSI with the small data information. Is stored (step S53).
- the small data information is notified from the terminal 10 to the MME 30 together with the Attach Request by the processing of step S52 and step S53.
- Default bearer creation is performed between the MME 30 and the S-GW 40 (step S54).
- the MME 30 notifies the terminal 10 of the Attach Accept via the base station 20 (step S55).
- the MME 30 sends the small data information together with the UE Context Release Command and S-TMSI to the base station 20 and a plurality of base stations around the base station 20 (for example, the base station in the tracking area where the terminal 10 is located). ) (Step S56). That is, the MME 30 notifies the small data information to the base station 20 before starting the small data RA procedure.
- the base station 20 transmits RRC Connection Release to the terminal 10 (step S57), while transmitting UE Context Release Complete to the MME 30 (step S58). As a result, the RRC connection set in step S51 is released.
- Sequence example 2 is shown in FIG. FIG. 6 is a sequence executed before small data to be transmitted from the terminal 10 is generated. That is, the terminal 10 of this example notifies small data information to the MME 30 in advance before the start of the small data RA procedure, as in the sequence example 1. For example, the terminal 10 notifies the MME 30 of the small data information in the “location registration procedure” executed before the start of the small data RA procedure.
- the “location registration procedure” is a procedure including a process in which the terminal 10 makes a location registration request (TAU (Tracking Area Update) Request). Further, since the location registration procedure is executed before the execution of the small data RA procedure corresponding to the “second random access procedure”, the location registration procedure is similar to the “attachment procedure”. Is equivalent to. Note that the processing in steps S51 and S56 to S58 in FIG. 6 is the same as that in FIG. Information exchanged in steps S61 to S63 in FIG. 6 corresponds to a control message.
- the terminal 10 transmits a TAU Request, RRC Connection Setup Complete, and small data information to the base station 20 (step S61). That is, the terminal 10 transmits small data information to the base station 20 together with the TAU Request.
- RRC Connection Setup Complete includes S-TMSI.
- the base station 20 forwards the TAU Request to the MME 30 and forms an Initial UE Message including S-TMSI and small data information and transmits it to the MME 30.
- the MME 30 associates with the S-TMSI and transmits the small data information. Is stored (step S62).
- the small data information is notified from the terminal 10 to the MME 30 together with the TAU Request by the processing of step S61 and step S62.
- the MME 30 notifies the terminal 10 of the TAU Accept via the base station 20 (step S63).
- Sequence example 3 is shown in FIG. FIG. 7 is a sequence subsequent to the sequence of FIG. 5 or FIG. 6, and in FIG. 7, the small data RA procedure is executed. Of the information exchanged in steps S72 to S81 in FIG. 7, information other than small data corresponds to a control message.
- step S71 when small data to be transmitted is generated (step S71), the terminal 10 transmits a Random Access Preamble to the base station 20 (step S72). On the other hand, the base station 20 transmits a Random Access Response to the terminal 10. Transmit (step S73).
- the terminal 10 transmits an RRC Connection Request including S-TMSI and a Small Data Indicator to the base station 20 (Step S74).
- the Small Data Indicator is an indicator indicating that the terminal 10 transmits small data, and is transmitted prior to the transmission of small data.
- the base station 20 has already received notification of the small data information from the MME 30 in step S56 (FIGS. 5 and 6) when it has received the small data indicator in step S74. Therefore, the base station 20 uses the small data information notified from the MME 30 to allocate communication resources to the small data, and sets the RRC Connection Setup including the allocation result (UL (Uplink) grant for small data transmission) to the terminal 10. (Step S75). For example, the base station 20 allocates more communication resources as the small data has a larger maximum data size. Further, for example, the base station 20 allocates communication resources that are earlier in time as the small data has a higher transmission priority. Also, for example, the base station 20 allocates communication resources with better radio quality for small data with higher required QoS.
- One unit of communication resource is defined by, for example, one unit of time and one unit of frequency, and may be called RE (Resource Element).
- the terminal 10 transmits small data to the base station 20 together with RRC Connection Setup Complete using the communication resource allocated by the base station 20 (step S76).
- the base station 20 forms an Initial UE Message including S-TMSI and small data and transmits it to the MME 30 (step S77).
- the MME 30 forms a GTP-U (GPRS (General Packet Radio Service) Tunneling Protocol for User Plane) including TEID (Tunnel Endpoint Identifier) and small data, and transmits it to the S-GW 40 (Step S78).
- GTP-U General Packet Radio Service
- TEID Tel Endpoint Identifier
- the S-GW 40 transmits DL (Downlink) Data Notification to the MME 30 (step S79).
- the MME 30 transmits a DL NAS (Non Access Stratum) Transport including the Release Command to the base station 20 (step S80).
- DL NAS Non Access Stratum
- the base station 20 transmits an RRC connection release to the terminal 10 (step S81).
- the RRC connection set in steps S74 and S75 is released. That is, the base station 20 releases the connection between the base station 20 and the terminal 10 when the reception of the small data transmitted from the terminal 10 is completed.
- “complete reception of small data” means that the small data transmitted from the terminal 10 has reached the S-GW 40.
- FIG. 8 is a sequence that follows the sequence of FIG. 5 or FIG. 6.
- the small data RA procedure is executed.
- FIG. 8 is a sequence in the case where the process of step S56 in FIGS. 5 and 6 is not performed, that is, in the case where the small data information is not notified from the MME 30 to the base station 20 in the attach procedure and the location registration procedure. It is.
- the processes of steps S82 and S83 are added to the sequence of FIG. Note that the processing in steps S71 to S81 in FIG. 8 is the same as that in FIG.
- the information exchanged in steps S82 and S83 in FIG. 8 corresponds to a control message.
- the base station 20 has not received the notification of the small data information from the MME 30 when the Small Data Indicator is received in Step S74. Therefore, the base station 20 transmits a notification request (Small Data Information Request) including the S-TMSI of the terminal 10 that is the acquisition target of the small data information to the MME 30 (step S82).
- a notification request Small Data Information Request
- the MME 30 that has received the notification request from the base station 20 transmits small data information corresponding to the S-TMSI requested from the base station 20 to the base station 20 together with the S-TMSI in response to the notification request (step). S83).
- Sequence example 5 is shown in FIG. FIG. 9 is a sequence that follows the sequence of FIG. 5 or FIG. 6.
- the small data RA procedure is executed. Note that the processing in steps S71 to S73 and S76 to S81 in FIG. 9 is the same as that in FIG.
- Information exchanged in steps S91 and S92 in FIG. 9 corresponds to a control message.
- the terminal 10 transmits the RRC Connection Request including S-TMSI and the changed small data information to the base station 20 (step S91). ). That is, when the small data information is changed, the small data information is notified from the terminal 10 to the base station 20. Note that the small data information transmitted in step S91 also serves as a small data indicator.
- the base station 20 gives priority to the small data using the changed small data information notified in step S91 in the small data RA procedure in preference to the small data information notified in the attach procedure or the location registration procedure. Allocate communication resources. Then, the base station 20 transmits an RRC connection setup including the allocation result (UL (Uplink) grant for small data transmission) to the terminal 10 (step S92).
- UL Uplink
- the terminal 10 transmits small data to the base station 20 in the small data RA procedure executed in response to the generation of uplink small data. Further, the terminal 10 notifies the MME 30 of the small data information before starting the small data RA procedure. For example, the terminal 10 notifies the MME 30 of the small data information together with the attach request in the attach procedure executed before the start of the small data RA procedure. Further, for example, the terminal 10 notifies the MME 30 of the small data information together with the location registration request in the location registration procedure executed before the start of the small data RA procedure.
- the small data RA procedure is executed every time small data is generated. Therefore, normally, the small data RA procedure is executed a plurality of times in response to the occurrence of the small data for one execution of the attach procedure or one execution of the location registration procedure. In the small data RA procedure, small data information is used for the generated small data. Then, the terminal 10 notifies the small data information in the attach procedure or the location registration procedure before the start of the small data RA procedure. Therefore, the small data information notified once in the attach procedure or the location registration procedure is repeatedly used in the small data RA procedure executed a plurality of times. This eliminates the need for the terminal 10 to notify the small data information every time small data is generated in the small data RA procedure. Therefore, the overhead of the control message can be reduced.
- the content of the small data information can be freely set without associating it with the random access preamble, it is possible to prevent the degree of freedom in selecting the random access preamble in the small data RA procedure.
- the overhead of the control message can be reduced without reducing the degree of freedom in selecting the random access preamble.
- the MME 30 notifies the small data information to the base station 20 before starting the small data RA procedure.
- the base station 20 can grasp the small data information in advance before the start of the small data RA procedure, it is possible to efficiently allocate communication resources to the small data.
- the small data information is information used for allocating communication resources for the small data
- the base station 20 allocates communication resources for the small data using the small data information notified from the MME 30.
- the terminal 10 transmits small data to the base station 20 using the communication resource allocated by the base station 20.
- the base station 20 releases the connection between the base station 20 and the terminal 10 when the reception of the small data transmitted from the terminal 10 using the communication resource allocated by the base station 20 is completed.
- the base station 20 can release the connection based on the small data information, the connection can be released at an appropriate timing after the communication of the small data is completed.
- the MME 30 when the MME 30 receives a notification request from the base station 20, the MME 30 notifies the small data information to the base station 20.
- the small data information can be notified to the base station 20 as required by the base station 20.
- the terminal 10 transmits a small data indicator indicating that the terminal 10 transmits small data to the base station 20 in the small data RA procedure.
- the base station 20 transmits a notification request to the MME 30 when it has not received notification of the small data information at the time of receiving the small data indicator.
- the base station 20 can receive the notification of the small data information when the small data is generated even when the notification of the small data information is not received before the start of the small data RA procedure.
- the terminal 10 when there is a change in the small data information, notifies the base station 20 of the changed small data information in the small data RA procedure.
- the base station 20 gives priority to the small data information notified by the terminal 10 before the start of the small data RA procedure and uses the changed small data information notified by the terminal 10 in the small data RA procedure to convert the small data into small data. Allocate communication resources to it.
- the base station 20 can allocate communication resources to the small data based on the latest small data information.
- the terminal 10, the base station 20, and the MME 30 do not necessarily need to be physically configured as illustrated.
- the specific form of distribution / integration of each unit is not limited to that shown in the figure, and all or a part thereof may be functionally or physically distributed / integrated in arbitrary units according to various loads or usage conditions. Can be configured.
- various processing functions performed in the terminal 10, the base station 20, and the MME 30 are performed on a CPU (Central Processing Unit) (or a microcomputer such as an MPU (Micro Processing Unit) or MCU (Micro Controller Unit)). All or any part may be executed.
- various processing functions may be executed in whole or in any part on a program that is analyzed and executed by a CPU (or a microcomputer such as an MPU or MCU) or on hardware based on wired logic. Good.
- the terminal 10, the base station 20, and the MME 30 can be realized by the following hardware configuration, for example.
- FIG. 10 is a diagram illustrating a hardware configuration example of the terminal.
- the terminal 100 includes an antenna 101, an RF (Radio Frequency) circuit 102, a processor 103, and a memory 104.
- the processor 103 include a CPU, a DSP (Digital Signal Processor), and an FPGA (Field Programmable Gate Array).
- the memory 104 include a RAM (Random Access Memory) such as SDRAM (Synchronous Dynamic Random Access Memory), a ROM (Read Only Memory), a flash memory, and the like.
- the various processing functions performed in the terminal 10 may be realized by the processor 103 executing programs stored in various memories such as a nonvolatile storage medium. That is, a program corresponding to each process executed by the transmission unit 11, the reception unit 13, and the control information processing unit 14 may be stored in the memory 104, and each program may be executed by the processor 103.
- the transmission unit 11 and the reception unit 13 are realized by the RF circuit 102 and the processor 103.
- the control information processing unit 14 is realized by the processor 103.
- the antenna 12 is realized by the antenna 101.
- FIG. 11 is a diagram illustrating a hardware configuration example of the base station.
- the base station 200 includes an antenna 201, an RF circuit 202, a processor 203, a network IF 204, and a memory 205.
- Examples of the processor 203 include a CPU, a DSP, an FPGA, and the like.
- Examples of the memory 205 include RAM such as SDRAM, ROM, flash memory, and the like.
- the various processing functions performed in the base station 20 may be realized by the processor 203 executing programs stored in various memories such as a nonvolatile storage medium. That is, a program corresponding to each process executed by the reception unit 22, the eNB communication control unit 23, and the transmission unit 25 may be stored in the memory 205, and each program may be executed by the processor 203.
- the receiving unit 22 and the transmitting unit 25 are realized by the RF circuit 202 and the processor 203.
- the eNB communication control unit 23 is realized by the processor 203.
- the storage unit 26 is realized by the memory 205.
- the antenna 21 is realized by the antenna 201.
- the network IF 24 is realized by the network IF 204.
- FIG. 12 is a diagram illustrating a hardware configuration example of the MME. As illustrated in FIG. 12, the MME 300 includes a network IF 301, a processor 302, and a memory 303.
- Examples of the processor 302 include a CPU, a DSP, and an FPGA.
- Examples of the memory 303 include RAM such as SDRAM, ROM, flash memory, and the like.
- the various processing functions performed by the MME 30 may be realized by the processor 302 executing programs stored in various memories such as a nonvolatile storage medium. That is, a program corresponding to each process executed by the MME communication control unit 32 may be stored in the memory 303, and each program may be executed by the processor 302. Further, the MME communication control unit 32 is realized by the processor 302. The storage unit 33 is realized by the memory 303. The network IFs 31 and 34 are realized by the network IF 301.
- the disclosed technology can be applied to user data other than small data.
- control information processing unit 10 base station 23 eNB communication control unit 30 MME 32 MME communication controller
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Databases & Information Systems (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
L'invention porte sur un système de communication qui peut réduire le surdébit associé à des messages de commande sans réduire le niveau de latitude disponible pour la sélection d'un préambule d'accès aléatoire. Ledit système de communication comprend un terminal (10), une station de base (20) et une MME (30). Avant qu'une procédure d'accès aléatoire, qui est exécutée en réponse à la génération de petites données de liaison montante, ne soit démarrée, le terminal (10) transmet à la station de base (20) un message de requête de fixation, un message d'achèvement d'établissement de connexion RRC et des informations de petites données. La station de base (20) transfère le message de requête de fixation à la MME (30), forme un message d'UE initial qui contient un S-TMSI et les informations de petites données, et transmet ledit message d'UE initial à la MME (30).
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| JP2015515707A JP6172267B2 (ja) | 2013-05-09 | 2013-05-09 | 通信システム及び通信方法 |
| PCT/JP2013/063079 WO2014181439A1 (fr) | 2013-05-09 | 2013-05-09 | Systeme de communication, dispositif terminal et procede de communication |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| PCT/JP2013/063079 WO2014181439A1 (fr) | 2013-05-09 | 2013-05-09 | Systeme de communication, dispositif terminal et procede de communication |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2014181439A1 true WO2014181439A1 (fr) | 2014-11-13 |
Family
ID=51866940
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/JP2013/063079 Ceased WO2014181439A1 (fr) | 2013-05-09 | 2013-05-09 | Systeme de communication, dispositif terminal et procede de communication |
Country Status (2)
| Country | Link |
|---|---|
| JP (1) | JP6172267B2 (fr) |
| WO (1) | WO2014181439A1 (fr) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JPWO2017017931A1 (ja) * | 2015-07-24 | 2017-08-03 | 日本電気株式会社 | 移動通信システム、mme、基地局、端末、及び通信方法 |
| JP2020198587A (ja) * | 2019-06-05 | 2020-12-10 | 富士ゼロックス株式会社 | 情報管理装置、端末装置、情報処理システム、情報管理プログラム及び情報処理プログラム |
| JPWO2023162130A1 (fr) * | 2022-02-25 | 2023-08-31 |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113039855B (zh) * | 2018-09-18 | 2024-10-29 | 上海诺基亚贝尔股份有限公司 | 用于数据传输的装置和方法 |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2012085010A (ja) * | 2010-10-07 | 2012-04-26 | Sony Corp | 無線端末、無線通信方法、および無線通信システム |
| WO2012137402A1 (fr) * | 2011-04-04 | 2012-10-11 | パナソニック株式会社 | Procédé de sélection de cellule, système de sélection de cellule, dispositif de communication et station de base |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR101518187B1 (ko) * | 2011-08-24 | 2015-05-15 | 엘지전자 주식회사 | Mtc 장치 트리거 기능에 관련된 상향링크 데이터를 송신하는 방법 및 장치 |
| KR102587135B1 (ko) * | 2011-09-30 | 2023-10-10 | 인터디지탈 패튼 홀딩스, 인크 | 감소된 채널 대역폭을 사용하는 장치 통신 |
-
2013
- 2013-05-09 WO PCT/JP2013/063079 patent/WO2014181439A1/fr not_active Ceased
- 2013-05-09 JP JP2015515707A patent/JP6172267B2/ja not_active Expired - Fee Related
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2012085010A (ja) * | 2010-10-07 | 2012-04-26 | Sony Corp | 無線端末、無線通信方法、および無線通信システム |
| WO2012137402A1 (fr) * | 2011-04-04 | 2012-10-11 | パナソニック株式会社 | Procédé de sélection de cellule, système de sélection de cellule, dispositif de communication et station de base |
Non-Patent Citations (3)
| Title |
|---|
| "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Machine-Type and other Mobile Data Applications Communications Enhancements (Release 12", 3GPP TR 23.887 V0.9.0, 24 April 2013 (2013-04-24) * |
| INSTITUTE FOR INFORMATION INDUSTRY (III: "Fast MTC data transmission procedure", 3GPP TSG-RAN WG2#70 R2- 102892, 10 May 2010 (2010-05-10) * |
| VIA TELECOM: "Access Procedure Enhancements for MTC Applications", 3GPP TSG-RAN WG2#70BIS R2- 103968, 28 June 2010 (2010-06-28) * |
Cited By (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JPWO2017017931A1 (ja) * | 2015-07-24 | 2017-08-03 | 日本電気株式会社 | 移動通信システム、mme、基地局、端末、及び通信方法 |
| JP2017220942A (ja) * | 2015-07-24 | 2017-12-14 | 日本電気株式会社 | 基地局、基地局の通信方法、端末、及び端末の通信方法 |
| CN107852596A (zh) * | 2015-07-24 | 2018-03-27 | 日本电气株式会社 | 移动通信系统、mme、终端和通信方法 |
| US11272337B2 (en) | 2015-07-24 | 2022-03-08 | Nec Corporation | Mobile communication system, MME, terminals and method for communication |
| US11445345B2 (en) | 2015-07-24 | 2022-09-13 | Nec Corporation | Mobile communication system, MME, terminals and method for communication |
| US12309678B2 (en) | 2015-07-24 | 2025-05-20 | Nec Corporation | Mobile communication system, MME, terminals and method for communication |
| JP2020198587A (ja) * | 2019-06-05 | 2020-12-10 | 富士ゼロックス株式会社 | 情報管理装置、端末装置、情報処理システム、情報管理プログラム及び情報処理プログラム |
| JP7334482B2 (ja) | 2019-06-05 | 2023-08-29 | 富士フイルムビジネスイノベーション株式会社 | 情報管理装置、端末装置、情報処理システム、情報管理プログラム及び情報処理プログラム |
| JPWO2023162130A1 (fr) * | 2022-02-25 | 2023-08-31 | ||
| JP7704287B2 (ja) | 2022-02-25 | 2025-07-08 | 日本電信電話株式会社 | データを収集するシステム、方法及びプログラム |
Also Published As
| Publication number | Publication date |
|---|---|
| JPWO2014181439A1 (ja) | 2017-02-23 |
| JP6172267B2 (ja) | 2017-08-02 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| KR101870850B1 (ko) | D2d 관련 정보 지시 및 d2d 송신 자원 확정 방법 및 장치 | |
| US20230189199A1 (en) | Positioning method and communication apparatus | |
| US11611988B2 (en) | Random access method and apparatus | |
| US9113370B2 (en) | Method and apparatus for handling a stationary user terminal in a network | |
| CN111757403A (zh) | 一种资源配置方法及通信装置 | |
| JP7540502B2 (ja) | 端末装置及び基地局 | |
| WO2017201741A1 (fr) | Procédé de commutation vers un noeud relais, et dispositif et système correspondants | |
| EP4052527B1 (fr) | Procédé et appareil de commutation de transmission de données entre des technologies d'accès radio pour une transmission de données précoce | |
| CN114642026B (zh) | 一种通信方法、装置及设备 | |
| CN114731672A (zh) | 信息传输方法、终端设备和网络设备 | |
| WO2021043416A1 (fr) | Transmissions de petites données à l'état inactif pour réseaux sans fil | |
| US11503664B2 (en) | Method, system and computer programs for the transmission of infrequent small data in a telecommunication system | |
| CN108141895B (zh) | 用户设备ue接入网络的方法、网络设备及第一ue | |
| JP6172267B2 (ja) | 通信システム及び通信方法 | |
| JP7690962B2 (ja) | 第2ネットワーク装置及び方法 | |
| EP4132035B1 (fr) | Procédé et appareil de communication | |
| CN112586029A (zh) | 用于在公共资源上进行数据传输的方法和装置 | |
| CN114641090A (zh) | 一种通信方法及通信装置 | |
| CN112770366B (zh) | 一种通信方法与通信装置 | |
| JP6079872B2 (ja) | 通信システム、基地局、端末装置及び通信方法 | |
| JP6107943B2 (ja) | 通信システム、端末装置及び通信方法 | |
| CN111869312A (zh) | 无线通信系统、基站、移动站和无线通信方法 | |
| WO2022267883A1 (fr) | Procédé et appareil de communication | |
| CN117998681A (zh) | 一种通信方法及装置 | |
| KR20180047171A (ko) | 이종 이동통신 규격 간의 상호 연동을 위한 시스템 및 방법 |
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: 13884233 Country of ref document: EP Kind code of ref document: A1 |
|
| ENP | Entry into the national phase |
Ref document number: 2015515707 Country of ref document: JP Kind code of ref document: A |
|
| NENP | Non-entry into the national phase |
Ref country code: DE |
|
| 122 | Ep: pct application non-entry in european phase |
Ref document number: 13884233 Country of ref document: EP Kind code of ref document: A1 |