Connection control, service processing method and apparatus

Abstract

The application provides a connection control method and device and a service processing method and device. The connection control method comprises the following steps: a first network element receives an uplink S1 message for establishing or resuming an S1 interface related to a user equipment (UE) from a second network element; and the first network element sends the downlink S1 message to the second network element, wherein the downlink S1 message contains one or a combination of the following information: first indication information and second indication information. Through the application, a method for indicating the second network element through an S1 message is provided.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of communication, in particular to a connection control method and device. BACKGROUND

[0002] In the inter-machine M2M communication system, UE (User Equipment) energy saving is crucial. In the prior art, when the UE in the RRC_IDLE state has data to be sent, the UE first triggers a random access process to establish or restore the RRC connection with the network. The UE can send the data together with the RRC connection establishment completion or RRC recovery completion message to the base station at the earliest, and then the UE will maintain the RRC_CONNECTED state for a period of time, waiting for the base station to release the UE. When the UE in the RRC_CONNECTED state has data to be sent, the UE may need to first initiate a random access because of the loss of time synchronization or the lack of uplink resources, and then send the data in Msg5 or the uplink air interface message after Msg5 to the base station after the completion of the random access process.

[0003] After the eNB receives the air interface message carrying the uplink data, it needs to trigger the S1 interface process to send the data to the core network. In the prior art, taking the CP (control plane) scheme as an example, the S1 interface process is as shown in Figure 1 Figure 1 It is an S1 interface process diagram in the related technology of the present application.

[0004] In the above-mentioned CP scheme of transmitting NAS PDU (Non-Access Stratum Protocol Data Unit), the terminal can include release assistance information (Release Assistance Information, RAI for short) in the UL NAS PDU, indicating whether the terminal has uplink data or expects downlink data. If it indicates that it expects downlink data (for example, the application layer confirms the UL NAS PDU), it may mean that the downlink data packet sent after the RAI is the last data packet of this application layer data exchange. The UE brings the UL NAS PDU to the eNB through the air interface message, and the eNB receives the air interface message with the UL NAS PDU. The eNB will send the S1-AP initial UE message to the MME, including the identification information (such as eNB UE S1AP ID) required by the eNB to establish the logical S1 connection related to the UE, and carrying the UL NAS PDU.

[0005] ​After the MME receives the uplink S1 message containing the UL NAS PDU, the MME forwards the UL NAS PDU to the core network. If the MME determines that the terminal does not expect downlink data according to the RAI information, and the MME does not have buffered downlink data and there is no S1-U interface, the MME can send a Connection Establishment Indication message to the eNB, the message containing the identification information (such as MME UE S1AP ID) required for the logical S1 connection related to the UE, for completing the establishment of the S1 interface related to the UE, and the message can also carry UE capability information to send to the eNB. After that, the MME can immediately send a UE Context Release Command to trigger connection release. If the MME determines that the terminal has expected downlink data according to the RAI information, the MME can send the data contained in the DL NAS PDU to the eNB through the DOWNLINK NAS TRANSPORT message after receiving the downlink data sent by the P-GW. If the MME also has buffered downlink data, these downlink data can be packaged in the DL NAS PDU together with the downlink data sent by the P-GW. If the MME determines that there will be no more downlink data according to the RAI and the MME also has no more buffered data, the MME will also immediately send a UE Context Release Command to trigger connection release.

[0006] After the eNB receives the DOWNLINK NAS TRANSPORT message, the eNB triggers the downlink data sending process of the air interface. If the eNB then receives the UE Context Release Command message, the eNB triggers the RRC connection release process to release the terminal from the RRC_CONNECTED state to the RRC_IDLE state.

[0007] In the related art, a method for optimizing the sending of service data is also proposed, Figure 2 is a method flowchart for sending service data in the related art of the present application. In the following random access process, the terminal transmits uplink data through Msg3, and then the terminal receives the conflict resolution ID carried by Msg4, determines that the conflict resolution is successful, and then the terminal considers that the uplink data sending is successful. The terminal can not need to transfer to the RRC_CONNECTED state, but can maintain in the RRC_IDLE state. This process can be referred to as an early data transmission (EDT) process.

[0008] In the EDT procedure, the terminal can send uplink data to the eNB in a Msg3 air interface message, and the terminal can determine whether to maintain in the RRC_IDLE state or to move to the RRC_CONNECTED state according to a Msg4 message sent by the eNB.

[0009] In the related art, it is not determined how the eNB selects different Msg4 to make the terminal enter the RRC_CONNECTED state or maintain in the RRC_IDLE state, and no effective solution is found. SUMMARY

[0010] Embodiments of the present application provide a connection control method and device, and a service processing method and device, to at least provide a method for indicating a second network element through an S1 message.

[0011] According to an embodiment of the present application, a connection control method is provided, comprising: a first network element receiving an uplink S1 message sent by a second network element for establishing or resuming an S1 interface related to a user equipment (UE); and the first network element sending a downlink S1 message to the second network element, wherein the downlink S1 message contains one or a combination of the following information: first indication information, and second indication information.

[0012] According to an embodiment of the present application, another connection control method is provided, comprising: a second network element receiving one or a combination of the following information sent by a first network element: first indication information, and second indication information; or, the second network element receiving user plane data sent by a third network element and one or a combination of the following information: first indication information, and second indication information; the second network element sending the user plane data to a UE through an air interface; and the second network element releasing or suspending an S1 interface related to the UE, or releasing all or part of evolved radio access bearers (E-RABs).

[0013] According to an embodiment of the present application, a service processing method is provided, comprising: a first network element receiving a low-layer protocol layer data unit sent by a user equipment (UE); a low-layer protocol layer of the first network element transferring a protocol layer data unit from a first logical channel and a protocol layer data unit from a second logical channel to a high-layer protocol layer; the high-layer protocol layer processing the protocol layer data unit from the first logical channel, and obtaining or resuming dedicated configuration information of the UE according to identification information contained in the protocol layer data unit; and the high-layer protocol layer transferring the dedicated configuration information and the protocol layer data unit of the second logical channel to the low-layer protocol layer, and the low-layer protocol layer processing the protocol layer data unit of the second logical channel according to the dedicated configuration information and transferring the protocol layer data unit to the high-layer protocol layer; or,

[0014] The first network element receives a low layer protocol layer data unit sent by the UE; a low layer protocol layer of the first network element delivers a protocol layer data unit from a first logical channel to a high layer protocol layer, and buffers a protocol layer data unit from a second logical channel; the high layer protocol layer processes the protocol layer data unit from the first logical channel, acquires or recovers dedicated configuration information of the UE according to identification information contained in the protocol layer data unit; and the high layer protocol layer delivers the dedicated configuration information to the low layer protocol layer, and the low layer protocol layer processes the protocol layer data unit of the second logical channel according to the dedicated configuration information and delivers it to the high layer protocol layer.

[0015] According to another embodiment of the present application, a connection control device is provided, which is applied to a first network element and comprises: a receiving module configured to receive an uplink S1 message sent by a second network element for establishing or resuming an S1 interface related to a user equipment (UE); and a sending module configured to send a downlink S1 message to the second network element, wherein the downlink S1 message contains one or a combination of the following information: first indication information, and second indication information.

[0016] According to another embodiment of the present application, another connection control device is provided, which is applied to a second network element and comprises: a receiving module configured to receive one or a combination of the following information sent by a first network element: first indication information, and second indication information; or, the second network element receives user plane data sent by a third network element and one or a combination of the following information: first indication information, and second indication information; a sending module configured to send the user plane data to a UE through an air interface; and a processing module configured to release or suspend an S1 interface related to the UE, or release all or part of evolved radio access bearers (E-RABs).

[0017] According to another embodiment of the present application, a service processing device is provided, which is applied to a first network element and comprises: a receiving module configured to receive a low layer protocol layer data unit sent by a UE; a low layer protocol layer configured to deliver a protocol layer data unit from a first logical channel and a protocol layer data unit from a second logical channel to a high layer protocol layer; and the high layer protocol layer is configured to process the protocol layer data unit from the first logical channel, acquire or recover dedicated configuration information of the UE according to identification information contained in the protocol layer data unit, deliver the dedicated configuration information and the protocol layer data unit of the second logical channel to the low layer protocol layer, and process the protocol layer data unit of the second logical channel according to the dedicated configuration information and deliver it to the high layer protocol layer; or,

[0018] The receiving module is configured to receive a low-layer protocol layer data unit sent by the UE; the low-layer protocol layer is configured to deliver a protocol layer data unit from a first logical channel to a high-layer protocol layer, and buffer a protocol layer data unit from a second logical channel; the high-layer protocol layer is configured to process the protocol layer data unit from the first logical channel, acquire or restore the dedicated configuration information of the UE according to identification information contained in the protocol layer data unit, and deliver the dedicated configuration information to the low-layer protocol layer; and the low-layer protocol layer is configured to process the buffered protocol layer data unit of the second logical channel according to the dedicated configuration information and deliver the protocol layer data unit to the high-layer protocol layer.

[0019] According to a further embodiment of the present application, a storage medium is also provided, which comprises a stored program, wherein the program performs any of the above-mentioned methods when executed.

[0020] According to a further embodiment of the present application, a processor is also provided, which is configured to execute a program, wherein the program performs any of the above-mentioned methods when executed.

[0021] According to the present application, the indication information is sent to the second network element after the first network element receives the uplink S1 message of the second network element for establishing or restoring the S1 interface related to the UE, thereby providing a method for indicating the second network element through the S1 message. BRIEF DESCRIPTION OF DRAWINGS

[0022] The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiments of the application and serve to explain the principles of the application, and do not limit the application. In the drawings:

[0023] Figure 1 is a S1 interface flowchart in the related art of the present application;

[0024] Figure 2 is a method flowchart for sending service data in the related art of the present application;

[0025] Figure 3 is a flowchart of a connection control method according to an embodiment of the present application;

[0026] Figure 4 is a flowchart of another connection control method according to an embodiment of the present application;

[0027] Figure 5 is a structural block diagram of a connection control device according to an embodiment of the present application;

[0028] Figure 6 is a structural block diagram of another connection control device according to an embodiment of the present application;

[0029] Figure 7 is a flow of the embodiment Figure 1 ;

[0030] Figure 8 is a flow of the embodiment Figure 2 ;

[0031] Figure 9 is a flow of the embodiment Figure 3 ;

[0032] Figure 10 is a flow of the embodiment Figure 4 ;

[0033] Figure 11 is a flow of the embodiment Figure 5 ;

[0034] Figure 12 is a flow of the embodiment Figure 6 ;

[0035] Figure 13 is a flow of the embodiment Figure 7 ;

[0036] Figure 14 is a flow of the embodiment Figure 8 ;

[0037] Figure 15 is a flow of the embodiment Figure 9 ;

[0038] Figure 16 is a flow of the embodiment Figure 10 ;

[0039] Figure 17 is a flow of the embodiment Figure 10 ; DETAILED DESCRIPTION

[0040] The present application will be described in detail below with reference to the accompanying drawings and embodiments. It should be noted that the embodiments in the present application and the features in the embodiments can be combined with each other without conflict.

[0041] It should be noted that the terms "first", "second" and the like in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and do not necessarily describe a specific order or sequence.

[0042] Embodiment 1

[0043] In this embodiment, a connection control method is provided, Figure 3 is a flowchart of a connection control method according to an embodiment of the present application, as shown in Figure 3 , the flow includes the following steps:

[0044] Step S302, the first network element receives an uplink S1 message from the second network element for establishing or resuming an S1 interface related to a user equipment (UE).

[0045] Step S304, the first network element sends a downlink S1 message to the second network element, wherein the downlink S1 message contains one or a combination of the following information: the first indication information, the second indication information.

[0046] Through the above steps, after the first network element receives the uplink S1 message from the second network element for establishing or resuming the S1 interface related to the UE, the indication information is sent to the second network element, thereby providing a method for indicating the second network element through the S1 message.

[0047] Optionally, the second network element is in one of the following states: a radio resource control idle (RRC_IDLE) state, a radio resource control inactive (RRC_INACTIVE) state.

[0048] Optionally, the first indication information is used to indicate the data state of the UE to the second network element, and the first indication information includes one or a combination of the following information: an end marker packet, whether the core network has buffered downlink data of the UE, whether the core network has buffered downlink data of the UE within a time length T.

[0049] Optionally, the first indication information is also used to implicitly indicate whether the second network element is allowed to actively initiate S1 connection release or suspension, or whether the second network element is allowed to release all or part of evolved radio access bearers (E-RABs).

[0050] Optionally, the second indication information is used to indicate whether the second network element is allowed to actively initiate S1 connection release or suspension, or whether the second network element is allowed to release all or part of evolved radio access bearers (E-RABs).

[0051] Optionally, the downlink S1 message includes related information of the S1 interface, wherein the related information of the S1 interface includes: an S1 interface identifier of the UE at the first network element side, and an S1 interface identifier of the UE at the second network element side.

[0052] Optionally, the first indication includes a timer, which is used to indicate the second network element to suspend the S1 interface related to the UE after receiving the first indication and waiting for the timer to expire.

[0053] Optionally, the set time length of the waiting timer is greater than or equal to 0.

[0054] Optionally, after the indication that the second network element can release or suspend the S1 interface related to the UE, the method further comprises: releasing or suspending the S1 interface related to the UE, or releasing all or part of the enhanced Radio Access Bearers (E-RABs), after the waiting timer expires.

[0055] Optionally, the first network element is a mobility management entity (MME), and the second network element is an access network.

[0056] A connection control method is provided in the embodiment, Figure 4 A flowchart of another connection control method according to an embodiment of the present application is shown in FIG. 4, which includes the following steps: Figure 4

[0057] In step S402, the second network element receives one or a combination of the following information from the first network element: the first indication information, the second indication information; or the second network element receives the user plane data and one or a combination of the following information from the third network element: the first indication information, the second indication information.

[0058] In step S404, the second network element sends the user plane data to the UE through an air interface.

[0059] In step S406, the second network element releases or suspends the S1 interface related to the UE, or releases all or part of the enhanced Radio Access Bearers (E-RABs).

[0060] Optionally, the second network element is in one of the following states: a radio resource control idle (RRC_IDLE) state, and a radio resource control inactive (RRC_INACTIVE) state.

[0061] Optionally, the first indication information is used to indicate the data state of the UE to the second network element, including one or a combination of the following: an end marker packet, whether the core network has buffered downlink data of the UE, and whether the core network has buffered downlink data of the UE within a time length T.

[0062] Optionally, the first indication information is also used to implicitly indicate whether the second network element is allowed to actively initiate S1 connection release or suspension, or whether the second network element is allowed to release all or part of the enhanced Radio Access Bearers (E-RABs).

[0063] Optionally, the second indication information is used to indicate whether the second network element is allowed to actively initiate S1 connection release or suspension, or whether the second network element is allowed to release all or part of the enhanced Radio Access Bearers (E-RABs).

[0064] ​Optionally, after receiving the indication information sent by the first network element or the third network element, the method further comprises: triggering, by the second network element, releasing or suspending the S1 interface related to the UE according to at least one of the following conditions: learning that the UE has no additional uplink data and only expects downlink acknowledgement data, completing receiving of downlink user plane data; learning that the UE has no additional uplink data, receiving downlink user plane data, and the data indicating that there is no additional downlink data; learning that the UE has no additional uplink data, receiving the indication of the first network element or the third network element about no additional downlink data; learning that the UE has no additional uplink data, receiving the indication of the first network element or the third network element about releasing or suspending the S1 interface.

[0065] Optionally, after releasing or suspending the S1 interface related to the UE according to the indication information, the method further comprises: sending, by the second network element, a Msg4 to the UE for indicating entering or maintaining in the RRC_IDLE state or the RRC_INACTIVE state.

[0066] Optionally, the first network element is a mobility management entity (MME), the second network element is an access network, and the third network element is a serving gateway (S-GW) or a PDN gateway (P-GW), and the first network element and the third network element belong to a core network.

[0067] In the embodiment, a service processing method is provided, including two implementation schemes, which are:

[0068] S11, receiving, by a first network element, a low-layer protocol layer data unit sent by a user equipment (UE);

[0069] S12, delivering, by a low-layer protocol layer of the first network element, a protocol layer data unit from a first logical channel and a protocol layer data unit from a second logical channel to a high-layer protocol layer;

[0070] S13, processing, by the high-layer protocol layer, the protocol layer data unit from the first logical channel, and obtaining or restoring dedicated configuration information of the UE according to identification information contained in the protocol layer data unit;

[0071] S14, delivering, by the high-layer protocol layer, the dedicated configuration information and the protocol layer data unit of the second logical channel to the low-layer protocol layer, and processing, by the low-layer protocol layer, the protocol layer data unit of the second logical channel according to the dedicated configuration information and delivering the protocol layer data unit of the second logical channel to the high-layer protocol layer.

[0072] Another scheme is:

[0073] S21, receiving, by a first network element, a low-layer protocol layer data unit sent by a user equipment (UE);

[0074] S22, delivering, by a low-layer protocol layer of the first network element, a protocol layer data unit from a first logical channel to a high-layer protocol layer, and buffering, by the low-layer protocol layer, a protocol layer data unit from a second logical channel;

[0075] S23, the high-layer protocol layer processes the protocol layer data unit from the first logical channel, and acquires or recovers the dedicated configuration information of the UE according to the identification information contained in the protocol layer data unit;

[0076] S24, the high-layer protocol layer delivers the dedicated configuration information to the low-layer protocol layer, and the low-layer protocol layer processes the protocol layer data unit of the second logical channel in the buffer according to the dedicated configuration information and delivers it to the high-layer protocol layer.

[0077] Optionally, the first network element is a base station; the low-layer protocol layer includes at least one of a physical layer and a medium access control (MAC) layer, and the high-layer protocol layer includes at least one of a radio link control (RLC) layer, a packet data convergence protocol (PDCP) layer and an RRC layer; and the identification information includes at least one of a recovery ID of the UE, a temporary mobile subscriber identity (S-TMSI) of the UE and a cell radio network temporary identifier (C-RNTI) of the UE.

[0078] Those skilled in the art can clearly understand that the method according to the above-mentioned embodiments can be realized by means of software and necessary general hardware platforms, of course, can also be realized by hardware, but in many cases, the former is a better implementation. Based on such understanding, the technical solutions of the present application can be embodied in the form of a software product, which is stored in a storage medium (such as a ROM / RAM, a magnetic disk, an optical disk), and includes a plurality of instructions for causing a terminal device (which can be a mobile phone, a computer, a server, or a network device, etc.) to execute the method described in each embodiment of the present application.

[0079] Embodiment 2

[0080] In this embodiment, a connection control device and a service processing device for implementing the above-mentioned embodiments and preferred embodiments are also provided, which have been described and will not be repeated. As used below, the term "module" can be a combination of software and / or hardware that implements a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, hardware or a combination of software and hardware is also possible and is contemplated.

[0081] Figure 5 is a structural block diagram of a connection control device according to an embodiment of the present application, which is applied to a first network element, such as a base station, as shown in the figure, the device includes: Figure 5

[0082] The receiving module 50 is configured to receive an uplink S1 message of a second network element for establishing or recovering an S1 interface related to a user equipment (UE).

[0083] ​The sending module 52 is configured to send a downlink S1 message to the second network element, wherein the downlink S1 message comprises one or a combination of the following information: the first indication information, and the second indication information.

[0084] Figure 6 is a structural block diagram of another connection control device according to an embodiment of the present application, as shown in the figure, comprising: Figure 6

[0085] The receiving module 60 is configured to receive one or a combination of the following information sent by the first network element: the first indication information, and the second indication information; or, the second network element receives user plane data sent by the third network element and one or a combination of the following information: the first indication information, and the second indication information.

[0086] The sending module 62 is configured to send the user plane data to the UE through an air interface.

[0087] The processing module 64 is configured to release or suspend an S1 interface related to the UE, or release all or part of evolved radio access bearers (E-RABs).

[0088] The embodiment further provides a service processing device applied to a first network element, comprising: a receiving module configured to receive a low-layer protocol layer data unit sent by a user equipment (UE); a low-layer protocol layer configured to transfer a protocol layer data unit from a first logical channel and a protocol layer data unit from a second logical channel to a high-layer protocol layer; and the high-layer protocol layer configured to process the protocol layer data unit from the first logical channel, obtain or restore dedicated configuration information of the UE according to identification information contained in the protocol layer data unit, and transfer the dedicated configuration information and the protocol layer data unit of the second logical channel to the low-layer protocol layer, which processes the protocol layer data unit of the second logical channel according to the dedicated configuration information and transfers it to the high-layer protocol layer.

[0089] Alternatively, the service processing device comprises: a receiving module configured to receive a low-layer protocol layer data unit sent by a UE; a low-layer protocol layer configured to transfer a protocol layer data unit from a first logical channel to a high-layer protocol layer and buffer a protocol layer data unit from a second logical channel; and the high-layer protocol layer configured to process the protocol layer data unit from the first logical channel, obtain or restore dedicated configuration information of the UE according to identification information contained in the protocol layer data unit, and transfer the dedicated configuration information to the low-layer protocol layer, which processes the buffered protocol layer data unit of the second logical channel according to the dedicated configuration information and transfers it to the high-layer protocol layer.

[0090] ​It should be noted that the above various modules can be implemented by software or hardware, and for the latter, the following implementation manners can be used, but are not limited thereto: all the above modules are located in the same processor; or the above various modules are located in different processors in any combination.

[0091] Embodiment 3

[0092] This embodiment is used to explain the scheme of the present application in detail.

[0093] The terminal can contain an indication (hereinafter referred to as indication 1) of whether there is more uplink data in Msg3, or contain an indication (hereinafter referred to as indication 2) of whether to preferentially establish an S1 interface or whether the terminal expects downlink confirmation of uplink data. Some companies also propose that the MME can contain another indication in the downlink S1 interface message, indicating whether the MME has additional downlink data to send to the terminal or whether the terminal is to be transferred to the RRC_CONNECTED state (hereinafter referred to as indication 3). The eNB provides information according to the indications 1 to 3, and on the basis of trying to use the existing S1 interface process, can perform the following operations:

[0094] The terminal uses the CP scheme, and the terminal sends the UL NAS PDU to the eNB in Msg3. The current standard discussion considers that the CP scheme does not support data segmentation transmission, and only when the to-be-sent uplink data matches the uplink grant (UL grant) obtained by the terminal, the terminal will use the EDT scheme, and the terminal will not indicate more uplink data in Msg3 (for example, indication 1 is not contained or indication 1 is negative).

[0095] Flow 1: If indication 2 is contained in Msg3, and the indication 2 indicates that the S1 interface is preferentially established or indicates that the terminal expects downlink confirmation of uplink data, the eNB can not send Msg4 to the terminal first, but trigger the S1 interface process first to send the uplink data to the core network. After the eNB receives the S1 interface downlink message (such as the DOWNLINK NAS TRANSPORT message) containing the DL NAS PDU, if the MME does not indicate that there is additional downlink data (for example, indication 3 is not contained or indication 3 is negative), the eNB sends the DL NAS PDU together with the conflict resolution ID to the terminal in Msg4, and the Msg4 indicates that the terminal maintains the RRC_IDLE state after the conflict resolution is successful; the MME can trigger the connection release according to the RAI information contained in the UL NAS PDU and the actual situation that there is no additional downlink data. Figure 7 Flow of the present embodiment Figure 1 .

[0096] Flow 2, Msg3 can not indicate that the terminal expects downlink acknowledgement for the uplink data (e.g. does not contain indication 2 or indication 2 is negative meaning), but considering that the MME can have buffered downlink data (MME has not triggered paging procedure according to DRX configuration), at this time the eNB can still not send Msg4 to the terminal, but first triggers S1 interface procedure to send uplink data to the core network, if the MME has no buffered downlink data, the MME will send a downlink S1 interface message to the eNB for completing S1 interface establishment (e.g. Connection Establishment Indication message), and does not indicate that there is additional downlink data, after the eNB receives the message, the eNB sends Msg4 containing only the conflict resolution ID to the terminal, and the Msg4 indicates that the terminal maintains RRC_IDLE state after successful conflict resolution; Figure 8 is the flow of the embodiment Figure 2 .

[0097] Flow 3, Msg3 can not indicate that the terminal expects downlink acknowledgement for the uplink data, but considering that the MME can have buffered downlink data (MME has not triggered paging procedure according to DRX configuration), at this time the eNB can still not send Msg4 to the terminal, but first triggers S1 interface procedure to send uplink data to the core network, if the MME has buffered downlink data, the MME will package the buffered data in DL NAS PDU and send it to the eNB through S1 interface downlink message (e.g. DOWNLINK NAS TRANSPORT message), if all buffered data can be packaged in the DL NAS PDU, the MME will not indicate that there is additional downlink data in the S1 interface downlink message. After the eNB receives the message, the eNB sends the DL NAS PDU together with the conflict resolution ID to the terminal in Msg4, and the Msg4 indicates that the terminal maintains RRC_IDLE state after successful conflict resolution; Figure 9 is the flow of the embodiment Figure 3 .

[0098] Flow 4, Msg3 can not indicate the terminal expects downlink acknowledgement for uplink data, but considering MME can have buffered downlink data (MME has not triggered paging procedure according to DRX configuration), eNB can still not send Msg4 to the terminal, but first trigger S1 interface procedure to send uplink data to core network, if MME has buffered downlink data, MME will package the buffered data in DL NAS PDU and send to eNB through S1 interface downlink message (such as DOWNLINK NAS TRANSPORT message), if the buffered data is large and cannot be packaged in one DL NAS PDU, MME will indicate that there is additional downlink data in the S1 interface downlink message. After receiving the message, eNB will include the DL NAS PDU and the conflict resolution ID in Msg4 and send to the terminal, which indicates the terminal to maintain in RRC_IDLE state but save C_RNTI after successful conflict resolution, or transfer to RRC_CONNECTED state. Figure 10 Flow of the embodiment Figure 4 .

[0099] The terminal uses UP scheme, the terminal multiplexes UL data and RRC message in Msg3 and sends to eNB, and the current standard discussion considers that UP scheme can support data segmentation transmission.

[0100] Flow 5, if the to-be-sent uplink data is greater than the uplink grant (UL grant) obtained by the terminal, the terminal can indicate more uplink data to be sent in Msg3 when transmitting uplink data using EDT scheme. Whether or not Msg3 indicates that the terminal expects downlink acknowledgement for uplink data, eNB can first send Msg4 containing conflict resolution ID to the terminal, which indicates the terminal to maintain in RRC_IDLE state but save C_RNTI after successful conflict resolution, or transfer to RRC_CONNECTED state. eNB can simultaneously trigger S1 interface procedure to send uplink data to core network. Figure 11 Flow of the embodiment Figure 5 .

[0101] Flow 6, if the uplink data to be sent matches the uplink grant (UL grant) obtained by the terminal, and the terminal can send the uplink data at one time, the terminal can not indicate in Msg3 that there is more uplink data to be sent (for example, indication 1 is not included or indication 1 is negative). It is also possible that the terminal does not indicate in Msg3 that it expects downlink confirmation of the uplink data, but considering that the network side can have buffered downlink data (according to the DRX configuration, the MME has not triggered the paging process), at this time the eNB can not send Msg4 to the terminal first, but trigger the S1 interface recovery process first. If the MME can learn that the network side has no buffered downlink data, the MME can indicate in the downlink S1 interface message (for example, the UE CONTEXT RESUME RESPONSE message) that there is no additional downlink data (for example, indication 3 is not included or indication 3 is negative). After receiving the message, the eNB can immediately send Msg4 containing only the conflict resolution ID to the terminal, and the Msg4 indicates that the terminal maintains the RRC_IDLE state after the conflict resolution is successful. Figure 12 is the flow of the embodiment Figure 6 .

[0102] Flow 7, if the uplink data to be sent matches the uplink grant (UL grant) obtained by the terminal, and the terminal can send the uplink data at one time, the terminal can not indicate in Msg3 that there is more uplink data to be sent (for example, indication 1 is not included or indication 1 is negative). If the terminal indicates in Msg3 that it expects downlink confirmation of the uplink data, the eNB can not send Msg4 to the terminal first, but trigger the S1 interface recovery process first. After receiving the downlink S1 interface message (for example, the UE CONTEXT RESUME RESPONSE message), even if the MME indicates in the message that the network side has no additional downlink data, the eNB can still further wait for the downlink confirmation (i.e., the downlink data) of the uplink data. When the downlink data is received, the eNB can multiplex the downlink data and the RRC message containing the conflict resolution ID in Msg4, and send the Msg4 to the terminal, and the Msg4 indicates that the terminal maintains the RRC_IDLE state after the conflict resolution is successful. Figure 13 is the flow of the embodiment Figure 7 .

[0103] Flow 8, if the uplink data to be sent matches the uplink grant (UL grant) obtained by the terminal, the terminal can send the uplink data at one time, and no more uplink data to be sent is indicated in Msg3 (for example, indication 1 is not included or indication 1 is negative). Regardless of whether the terminal expects downlink confirmation of the uplink data is indicated in Msg3, the eNB can not send Msg4 to the terminal first, but trigger the S1 interface recovery process first. If the MME can learn that there is buffered downlink data on the network side, the MME can indicate that there is additional downlink data in the downlink S1 interface message (for example, the UE CONTEXT RESUME RESPONSE message), and the eNB can immediately send Msg4 containing the conflict resolution ID to the terminal after receiving the downlink S1 interface message. The Msg4 indicates that the terminal remains in the RRC_IDLE state but saves the C_RNTI after the conflict resolution is successful, or moves to the RRC_CONNECTED state. Figure 14 Flow of the embodiment Figure 8 .

[0104] In the flow 1 to flow 3 of the CP scheme, it can be seen that, regardless of whether the eNB waits to receive the downlink S1-AP interface message before sending Msg4, the eNB can receive an S1-AP interface message for triggering connection release afterwards. Unlike the legacy process, the air interface connection between the terminal and the eNB is in the RRC_IDLE state at this time, that is, there is a situation of inconsistency between the air interface and the S1 interface state, and the eNB can determine that an exception occurs because of the inconsistency between the air interface and the S1 interface state of the terminal after receiving the connection release message.

[0105] In the flow 6 and flow 7 of the UP scheme, there is also a problem of inconsistency between the air interface and the S1 interface state of the terminal, and it is not likely to appear uplink and downlink data interaction at this time, and the S1 interface state maintenance can cause unnecessary resource waste. In addition, in the existing process, the release and suspension of the S1 interface are usually triggered by the eNB, for example, the eNB will release or suspend the air interface and the S1 interface at the same time after the inactivity timer maintained by the eNB expires. In the above-mentioned flow, since the air interface between the eNB and the UE is already in the RRC_IDLE state, the eNB will not maintain the air interface inactivity timer, and the eNB will not have the trigger condition to release the S1 interface. In this scenario, it is necessary to consider defining a new time or trigger condition for releasing or suspending the S1 interface.

[0106] The embodiment is to solve the inconsistency between the air interface and the S1 interface connection in the above-mentioned scheme, and the following scheme is proposed:

[0107] In the UP scheme, after the MME receives the uplink S1 message for establishing or resuming the UE-related S1 interface containing data, if it judges that there is no downlink data buffered in the core network, etc., the MME can instruct to release or suspend the UE-related S1 interface, and the subsequent eNB can actively initiate the S1 interface suspension process.

[0108] Preferably, the MME can include a release instruction in the downlink S1 interface message responding to the uplink S1 interface establishment or resumption message, instructing the eNB to actively initiate the S1 connection suspension or E-RAB release.

[0109] A connection control method on the base station side, comprising:

[0110] In the UP scheme, when the base station performs the establishment or resumption of the UE-related S1 interface, the MME instruction is received, and the S1 interface release or suspension process is triggered according to the MME instruction.

[0111] Preferably, the base station triggers the release or suspension of the S1 interface when one or a combination of the following conditions occurs:

[0112] The base station learns that the UE has no additional uplink data, and only expects downlink confirmation data, and the base station has received downlink user plane data;

[0113] The base station learns that the UE has no additional uplink data, and the base station receives downlink user plane data indicating that there is no additional data in the downlink;

[0114] The base station learns that the UE has no additional uplink data, and the base station receives the MME indication that there is no additional downlink data;

[0115] The base station learns that the UE has no additional uplink data, and the base station receives the MME instruction to release or suspend the S1 interface.

[0116] The embodiment also includes the following examples:

[0117] If the downlink S1 interface message sent by the MME in response to the uplink S1 interface establishment or resumption message indicates to release the S1 interface (for example, the downlink S1 interface message contains a release instruction, or the downlink S1 interface message is a release command message), the eNB sends a Msg4 indicating that the terminal is maintained in the RRC_IDLE state to the terminal.

[0118] If the downlink S1 interface message sent by the MME in response to the uplink S1 interface establishment or resumption message indicates to establish or resume the S1 interface, the eNB sends a Msg4 indicating that the terminal moves to the RRC_IDLE state with the C_RNTI saved or moves to the RRC_CONNECTED state to the terminal.

[0119] Embodiment 4

[0120] Figure 15 is the flow of this embodiment Figure 9 , Figure 16 is the flow of this embodiment Figure 10 , respectively illustrates a complete example of this embodiment, Figure 15 In this embodiment, the base station directly sends Msg4 to the UE after receiving the Msg3 carrying the uplink indication information (UL data indication), and the UE enters the connected state after receiving the Msg4. Figure 16 In this embodiment, the Msg3 does not carry the uplink indication information.

[0121] Embodiment 5

[0122] In the UP scheme, the first network element receives the Msg3 sent by the UE, wherein the Msg3 multiplexes multiple MAC layer service data units (MAC SDUs) of RRC messages from the common control channel (CCCH) and user data of the dedicated traffic channel (DTCH). The first network element first analyzes the MAC SDU from the CCCH, but because the first network element has not obtained the resume ID (Resume ID) of the UE at this time, the first network element cannot analyze the MAC SDU from the DTCH.

[0123] The first network element will adopt the following operations:

[0124] The MAC layer of the first network element delivers the MAC SDU from the CCCH and the MAC SDU from the DTCH to the upper layer together;

[0125] After the upper layer processes the MAC SDU from the CCCH and obtains the resume ID of the UE, the context and the logical channel configuration of the UE are restored;

[0126] The upper layer delivers the logical channel configuration information and the MAC SDU of the DTCH to the MAC layer, and the MAC layer can correctly process the MAC SDU of the DTCH and correctly send it to the upper layer.

[0127] Alternatively,

[0128] The MAC layer of the first network element only delivers the MAC SDU from the CCCH to the upper layer, and buffers the MAC SDU from the DTCH;

[0129] After the upper layer processes the MAC SDU from the CCCH and obtains the resume ID of the UE, the context and the logical channel configuration of the UE are restored;

[0130] The higher layer provides the logical channel configuration information to the MAC layer, and the MAC layer processes the buffered MAC SDU of the DTCH according to the configuration information and transmits it to the higher layer.

[0131] Embodiment 6

[0132] Figure 17 is the flow of this embodiment Figure 10 One, the scheme of the embodiment Figure 4 Corresponding to the scheme of the embodiment, the second network element (eNB) can receive the indication information of the first network element and / or the third network element in the core network (Core).

[0133] Embodiment 7

[0134] The embodiment of the application further provides a storage medium, which comprises a stored program, wherein the program performs the method of any one of the above when running.

[0135] Optionally, in the embodiment, the storage medium can be arranged to store program code for performing the following steps:

[0136] S1, receiving an uplink S1 message of the second network element for establishing or resuming an S1 interface related to a user equipment (UE);

[0137] S2, sending a downlink S1 message to the second network element, wherein the downlink S1 message comprises one or a combination of the following information: the first indication information, the second indication information.

[0138] Optionally, in the embodiment, the storage medium can include but is not limited to: a U disk, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk or an optical disk and various storage program codes.

[0139] The embodiment of the application further provides a processor for running a program, wherein the program performs the steps in the method of any one of the above when running.

[0140] Optionally, in the embodiment, the program is used to perform the following steps:

[0141] S1, receiving an uplink S1 message of the second network element for establishing or resuming an S1 interface related to a user equipment (UE);

[0142] S2, sending a downlink S1 message to the second network element, wherein the downlink S1 message comprises one or a combination of the following information: the first indication information, the second indication information.

[0143] Optionally, the specific examples in the present embodiment can refer to the examples described in the above embodiments and optional implementation manners, and the present embodiment will not be described here again.

[0144] Obviously, those skilled in the art should understand that the modules or steps of the present application described above can be realized by general computing devices, which can be centralized on a single computing device or distributed on a network composed of multiple computing devices, and optionally, they can be realized by program codes executable by the computing devices, so that they can be stored in storage devices and executed by the computing devices, and in some cases, the steps shown or described can be executed in different order, or they can be respectively manufactured into individual integrated circuit modules, or multiple modules or steps among them can be manufactured into a single integrated circuit module to realize. Thus, the present application is not limited to any specific combination of hardware and software.

[0145] The above only describes the preferred embodiments of the present application and is not intended to limit the present application. Those skilled in the art can make various modifications and changes to the present application. Any modification, equivalent replacement, improvement, etc. within the principles of the present application shall be included in the protection scope of the present application.

Claims

1. A service processing method characterized by, Comprising: The first network element receives low layer protocol layer data units sent by a user equipment (UE); The low layer protocol layer of the first network element delivers protocol layer data units from a first logical channel and protocol layer data units from a second logical channel to a high layer protocol layer; The high layer protocol layer processes the protocol layer data units from the first logical channel, and acquires or recovers dedicated configuration information of the UE according to identification information contained in the protocol layer data units; The high layer protocol layer delivers the dedicated configuration information and the protocol layer data units of the second logical channel to the low layer protocol layer, and the low layer protocol layer processes the protocol layer data units of the second logical channel according to the dedicated configuration information and delivers them to the high layer protocol layer; Or, The first network element receives low layer protocol layer data units sent by a user equipment (UE); The low layer protocol layer of the first network element delivers protocol layer data units from a first logical channel to a high layer protocol layer, and buffers protocol layer data units from a second logical channel; The high layer protocol layer processes the protocol layer data units from the first logical channel, and acquires or recovers dedicated configuration information of the UE according to identification information contained in the protocol layer data units; The high layer protocol layer delivers the dedicated configuration information to the low layer protocol layer, and the low layer protocol layer processes the buffered protocol layer data units of the second logical channel according to the dedicated configuration information and delivers them to the high layer protocol layer; When the downlink S1 interface message sent by the first network element in response to the uplink S1 interface establishment or recovery message indicates to release the downlink S1 interface, the second network element sends a Msg4 indicating that the UE is maintained in an RRC_IDLE state to the UE; When the downlink S1 interface message sent by the first network element in response to the uplink S1 interface establishment or recovery message indicates to establish or recover the downlink S1 interface, the second network element sends a Msg4 indicating that the UE is shifted to an RRC_IDLE state with a saved C_RNTI or shifted to an RRC_CONNECTED state to the UE.

2. The method of claim 1, wherein, The first network element is a base station; the low layer protocol layer includes at least one of a physical layer and a medium access control (MAC) layer, and the high layer protocol layer includes at least one of a radio link control (RLC) layer, a packet data convergence protocol (PDCP) layer, and an RRC layer; and the identification information includes at least one of a recovery ID of the UE, a temporary mobile subscriber identity (S-TMSI) of the UE, and a cell radio network temporary identifier (C-RNTI) of the UE.

3. The method of claim 1, wherein, The protocol layer data units of the first logical channel include a medium access control (MAC) service data unit (SDU) of a common control channel (CCCH), and the protocol layer data units of the second logical channel include a plurality of MAC SDUs of a dedicated traffic channel (DTCH).

4. A service processing apparatus characterized by comprising: Applied to a first network element, comprising: A receiving module configured to receive low layer protocol layer data units sent by a user equipment (UE); A low layer protocol layer configured to deliver protocol layer data units from a first logical channel and protocol layer data units from a second logical channel to a high layer protocol layer; The high layer protocol layer processes the protocol layer data units from the first logical channel, and acquires or recovers dedicated configuration information of the UE according to identification information contained in the protocol layer data units; The high layer protocol layer delivers the dedicated configuration information and the protocol layer data units of the second logical channel to the low layer protocol layer, and the low layer protocol layer processes the protocol layer data units of the second logical channel according to the dedicated configuration information and delivers them to the high layer protocol layer; Or, The first network element receives low layer protocol layer data units sent by a user equipment (UE); The low layer protocol layer of the first network element delivers protocol layer data units from a first logical channel to a high layer protocol layer, and buffers protocol layer data units from a second logical channel; The high layer protocol layer processes the protocol layer data units from the first logical channel, and acquires or recovers dedicated configuration information of the UE according to identification information contained in the protocol layer data units; The high layer protocol layer delivers the dedicated configuration information to the low layer protocol layer, and the low layer protocol layer processes the buffered protocol layer data units of the second logical channel according to the dedicated configuration information and delivers them to the high layer protocol layer; When the downlink S1 interface message sent by the first network element in response to the uplink S1 interface establishment or recovery message indicates to release the downlink S1 interface, the second network element sends a Msg4 indicating that the UE is maintained in an RRC_IDLE state to the UE; When the downlink S1 interface message sent by the first network element in response to the uplink S1 interface establishment or recovery message indicates to establish or recover the downlink S1 interface, the second network element sends a Msg4 indicating that the UE is shifted to an RRC_IDLE state with a saved C_RNTI or shifted to an RRC_CONNECTED state to the UE. The first network element is a base station; the low layer protocol layer includes at least one of a physical layer and a medium access control (MAC) layer, and the high layer protocol layer includes at least one of a radio link control (RLC) layer, a packet data convergence protocol (PDCP) layer, and an RRC layer; and the identification information includes at least one of a recovery ID of the UE, a temporary mobile subscriber identity (S-TMSI) of the UE, and a cell radio network temporary identifier (C-RNTI) of the UE. The protocol layer data units of the first logical channel include a medium access control (MAC) service data unit (SDU) of a common control channel (CCCH), and the protocol layer data units of the second logical channel include a plurality of MAC SDUs of a dedicated traffic channel (DTCH). The high-layer protocol layer is configured to process the protocol layer data units from the first logical channel, obtain or restore the dedicated configuration information of the UE according to the identification information contained in the protocol layer data units, and deliver the dedicated configuration information and the protocol layer data units of the second logical channel to the low-layer protocol layer. The receiving module is configured to receive the low-layer protocol layer data units sent by the UE. The low-layer protocol layer is configured to deliver the protocol layer data units from the first logical channel to the high-layer protocol layer and buffer the protocol layer data units of the second logical channel. The high-layer protocol layer is configured to process the protocol layer data units from the first logical channel, obtain or restore the dedicated configuration information of the UE according to the identification information contained in the protocol layer data units, and deliver the dedicated configuration information to the low-layer protocol layer, which processes the buffered protocol layer data units of the second logical channel according to the dedicated configuration information and delivers the protocol layer data units to the high-layer protocol layer. When the downlink S1 interface message sent by the first network element in response to the uplink S1 interface establishment or recovery message indicates that the downlink S1 interface is released, the second network element sends a Msg4 indicating that the UE is maintained in an RRC_IDLE state to the UE. When the downlink S1 interface message sent by the first network element in response to the uplink S1 interface establishment or recovery message indicates that the downlink S1 interface is established or recovered, the second network element sends a Msg4 indicating that the UE is transferred to an RRC_IDLE state in which a C_RNTI is saved or to an RRC_CONNECTED state to the UE.

5. The apparatus of claim 4, wherein, The first network element is a base station; the low-layer protocol layer includes at least one of a physical layer and a medium access control (MAC) layer, and the high-layer protocol layer includes at least one of a radio link control (RLC) layer, a packet data convergence protocol (PDCP) layer, and an RRC layer; and the identification information includes at least one of a recovery ID of the UE, a temporary mobile subscriber identity (S-TMSI) of the UE, and a cell radio network temporary identifier (C-RNTI) of the UE.

6. The apparatus of claim 4, wherein, The protocol layer data units of the first logical channel include medium access control (MAC) service data units (SDUs) of a common control channel (CCCH), and the protocol layer data units of the second logical channel include multiple MAC SDUs of a dedicated traffic channel (DTCH).

7. A computer-readable storage medium, characterized in that, The storage medium includes a stored program, and the program is configured to perform the method in any one of claims 1 to 3 when executed.

Images