CN108617022B - Message transmission method and device - Google Patents
Message transmission method and device Download PDFInfo
- Publication number
- CN108617022B CN108617022B CN201710014019.5A CN201710014019A CN108617022B CN 108617022 B CN108617022 B CN 108617022B CN 201710014019 A CN201710014019 A CN 201710014019A CN 108617022 B CN108617022 B CN 108617022B
- Authority
- CN
- China
- Prior art keywords
- functional entity
- message
- connection identifier
- target
- entity
- 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.)
- Active
Links
Abstract
The invention discloses a message transmission method and a message transmission device. In the invention, on one hand, the MM functional entity receives the message sent by the SM functional entity, wherein the message comprises a connection identifier for routing the SM message; and the MM functional entity performs corresponding processing according to the connection identifier. On the other hand, the SM functional entity sends a message to the MM functional entity, wherein the message comprises a connection identifier for routing the SM message; and the SM functional entity receives a response message sent by the MM functional entity according to the message. The invention realizes the message transmission under the framework of separating the MM functional entity and the SM functional entity.
Description
Technical Field
The present invention relates to the field of communications technologies, and in particular, to a method and an apparatus for transmitting a message.
Background
In an Evolved Packet System (EPS) System shown in fig. 1, a Mobility Management Entity (MME) supports both Mobility Management (MM) functions (such as attach, tracking area update, etc.) and Session Management (SM) functions (such as Packet Data Network (PDN) connection establishment, modification, deletion, etc.). MM messages and SM messages sent by a terminal (UE, i.e. user equipment) are both terminated at the MME and processed by the MME.
in order to improve the modularization degree of the network, the MM function and the SM function are separated from the MME, and a network architecture in which the MM function and the SM function are separated is shown in fig. 2. The MM function entity is a component of the general control network function, and the general control network function terminates the MM message and the SM message, that is, the MM message and the SM message sent by the UE will both terminate at the MM function entity. The MM functional entity processes the MM message, determines a target SM functional entity by analyzing the SM message, and forwards the SM message to the determined target SM functional entity.
In a system architecture with separated MM function and SM function, how to perform message transmission is a problem that needs to be solved at present, especially when there are multiple SM function entities providing services for the UE.
disclosure of Invention
the embodiment of the application provides a message transmission method and device.
The message transmission method provided by the embodiment of the application comprises the following steps:
The MM functional entity receives a message sent by the SM functional entity, wherein the message comprises a connection identifier for routing the SM message;
And the MM functional entity performs corresponding processing according to the connection identifier.
a message transmission method provided in another embodiment of the present application includes:
the SM functional entity sends a message to the MM functional entity, wherein the message comprises a connection identifier for routing the SM message;
and the SM functional entity receives a response message sent by the MM functional entity after corresponding processing is carried out by the MM functional entity according to the connection identifier included in the message.
the MM functional entity device provided in the embodiment of the present application includes:
A receiving module, configured to receive a message sent by an SM functional entity, where the message includes a connection identifier for routing the SM message;
and the processing module is used for carrying out corresponding processing according to the connection identifier.
The SM function entity equipment that embodiment of this application provided includes:
A sending module, configured to send a message to the MM function entity, where the message includes a connection identifier for routing an SM message;
A receiving module, configured to receive a response message sent by the MM functional entity after performing corresponding processing according to the connection identifier included in the message.
an embodiment of the present application provides a communication device, including: a network interface, a processor, and a memory;
the network interface is used for receiving and/or sending messages;
the memory to store computer program instructions;
the processor, coupled to the memory, is configured to read the computer program instructions stored in the memory and execute the method implemented by the MM functional entity provided in the foregoing embodiments.
Another communication device provided in an embodiment of the present application includes: a network interface, a processor, and a memory;
the network interface is used for receiving and/or sending messages;
the memory to store computer program instructions;
The processor, coupled to the memory, is configured to read the computer program instructions stored in the memory and execute the method implemented by the SM functional entity provided in the foregoing embodiments.
Drawings
FIG. 1 is a diagram illustrating an EPS system architecture in the prior art;
FIG. 2 is a diagram illustrating a prior art architecture in which MM functions are separated from SM functions;
fig. 3 is a schematic flow chart of SM message routing on the MM function entity side in the embodiment of the present application;
fig. 4 is a schematic flow chart of SM message routing on the SM function entity side in the embodiment of the present application;
Fig. 5 is a schematic signaling flow diagram of SM message routing provided in the embodiment of the present application;
Fig. 6 is a second schematic signaling flow diagram of SM message routing according to the embodiment of the present application;
fig. 7 is a schematic diagram illustrating a deletion process of connection identifier related information in a PDU session release process in an embodiment of the present application;
fig. 8 is a schematic process diagram of selecting a target SM functional entity for handover by an SM functional entity in the embodiment of the present application;
fig. 9 is a schematic diagram illustrating a process of selecting a target SM functional entity by a MM functional entity in an embodiment of the present application;
Fig. 10 is a schematic structural diagram of an MM functional entity device according to an embodiment of the present application;
fig. 11 is a schematic structural diagram of an SM functional entity device provided in an embodiment of the present application.
Detailed Description
The embodiment of the application provides a message transmission method, which is applied to a network architecture with separated MM function and SM function. Embodiments of the present invention will be described in detail below with reference to the accompanying drawings.
in an embodiment of the present application, a connection identifier is defined, where the connection identifier is used for routing an SM message. The connection identifier may be used to identify messages belonging to the same session, and the MM functional entity may determine a target SM functional entity for SM messages according to the connection identifier. The connection identifier is carried in the message exchanged between the MM and the SM. The session may be a Packet Data Unit (PDU) session.
the connection identifier is assigned by the MM functional entity and is sent by the MM functional entity to the SM functional entity and the terminal during SM message transmission. The MM functional entity, the SM functional entity, and the terminal may store the related information of the connection identifier, specifically:
The MM functional entity stores the connection identifier and SM functional entity information corresponding to the connection identifier (hereinafter referred to as mapping relationship information between the connection identifier and the SM functional entity), for example, one mapping relationship may be expressed as < connection identifier, SM functional entity address >; the mapping relation information can be stored in the context of the terminal;
the SM functional entity stores session information and connection identifier information corresponding to the session information (hereinafter referred to as mapping relationship information between session and connection identifiers), for example, one mapping relationship may be expressed as < PDU session identifier, connection identifier >; the mapping relation information can be stored in the context of the terminal;
-storing mapping information between session and connection identities at the terminal, e.g. a mapping can be expressed as < PDU session identity, connection identity >.
Fig. 3 schematically shows a message transmission flow. As shown in the figure, in S301, the SM functional entity sends a message to the MM functional entity, where the message includes a connection identifier for routing the SM message; in S302, the MM functional entity performs corresponding processing according to the connection identifier in the message. The transmission process of the SM message, the session release process, and the handover process of the SM functional entity may all perform information interaction according to the flow shown in fig. 3.
Fig. 4 exemplarily shows a message transmission flow. As shown in the figure, in S401, the MM functional entity sends a request message to the SM functional entity, where the request message includes a first SM message and a connection identifier for routing the first SM message; in S402, the SM functional entity sends a reply message to the MM functional entity according to the request message, where the reply message includes the second SM message and the connection identifier. The SM message transmission process may perform information interaction according to the flow shown in fig. 4.
The transmission process of the SM message may include a session setup process of the SM message, a session modification process of the SM message, and a session release process of the SM message.
Fig. 5 exemplarily shows a session establishment procedure of the SM message. As shown in fig. 5, the process may include:
S501: the UE sends a Radio Resource Control (RRC) message to the Radio access network, where the RRC message includes an SM message 1, and the SM message 1 may include information required for selecting an SM functional entity.
S502: after receiving the RRC message, the radio access network sends a NG2 interface message to the MM functional entity, where the parameters carried in the NG2 interface message may include parameters provided by the UE in the RRC message.
s503: the MM functional entity receives the NG2 interface message, because the message does not carry the connection identifier for routing the SM message, the MM functional entity selects the SM functional entity for SM message 1 in the NG2 message according to the information which is carried in the message and is needed for selecting the SM functional entity, allocates the connection identifier for routing the SM message, and sends a request message to the selected SM functional entity, wherein the request message can comprise the SM message 1 and the allocated connection identifier. The MM functional entity stores mapping relationship information between the allocated routing identity and the selected SM functional entity in the context of the UE.
s504: after receiving the request message, the SM functional entity obtains the connection identifier from the request message, locally stores mapping relationship information between the PDU session and the connection identifier, processes the SM message 1 contained in the request message, generates the SM message 2 according to the processing result, and returns a reply message to the MM functional entity, where the reply message may include the SM message 2 and the connection identifier. The connection identifier carried in the reply message is the same as the connection identifier carried in the request message, and the SM message 1 carried in the request message and the SM message 2 carried in the reply message belong to the same PDU session.
S505: after receiving the reply message, the MM functional entity determines information of a radio access network of the UE according to the context of the UE, and sends an NG2 interface message to the radio access network, where the NG2 interface message includes an SM message 2 and a connection identifier, and the connection identifier in the NG2 interface message is the same as the connection identifier in the reply message.
S506: after receiving the NG2 interface message, the radio access network sends an RRC message to the UE, where the RRC message may include SM message 2 and a connection identifier. After receiving the RRC message, the UE locally stores mapping relationship information between the PDU session to which the SM message 2 belongs and the connection identifier.
in a further embodiment, when the UE requests to establish a new PDU session, the connection identity is not included in the SM message when the UE sends the PDU session request, since different PDU sessions may be served by different SM functional entities. In this case, in S502, after the MM functional entity receives the NG2 interface message, since the MM functional entity does not include the connection identifier therein, the MM functional entity selects one SM functional entity, and if the selected SM functional entity is already included in the mapping relationship information (that is, the SM functional entity in a certain mapping relationship is the same as the currently selected SM functional entity), the MM functional entity carries the connection identifier corresponding to the SM functional entity in the mapping relationship in the NG2 message.
fig. 6 exemplarily shows a session modification procedure of the SM message. As shown in fig. 6, after the PDU session is established (the setup procedure of the PDU session may be as shown in fig. 5), the UE may initiate a PDU session modification procedure, which may include:
S601: the UE sends an RRC message to the radio access network, which includes the SM message 3 and a connection identity for routing the SM message 2. In this step, the UE searches for locally stored mapping relationship information between the PDU session and the connection identifier according to the PDU session to which the SM message 3 belongs, obtains a corresponding connection identifier, and carries the connection identifier in the RRC message.
S602: after receiving the RRC message, the radio access network sends an NG2 interface message to the MM functional entity, where the NG2 interface message includes an SM message 3 and a connection identifier.
S603: the MM functional entity receives the NG2 interface message, because the message carries the connection identifier for routing the SM message 3, the MM functional entity queries the mapping relationship information between the locally stored SM functional entity and the connection identifier according to the connection identifier to obtain the SM functional entity corresponding to the connection identifier, and the MM functional entity sends a request message to the queried SM functional entity, wherein the request message may include the SM message 3 and the connection identifier. In specific implementation, the MM functional entity may query, according to the identifier of the terminal, the SM functional entity corresponding to the connection identifier from mapping relationship information between the SM functional entity and the connection identifier stored in the context of the terminal.
S604: after receiving the request message, the SM functional entity processes the SM message 3 contained in the request message, generates an SM message 4 according to the processing result, and returns a reply message to the MM functional entity, where the reply message may include the SM message 4 and the connection identifier. The connection identifier carried in the reply message is the same as the connection identifier carried in the request message, and the SM message 3 carried in the request message and the SM message 4 carried in the reply message belong to the same PDU session.
s605: after receiving the reply message, the MM functional entity determines the radio access network currently connected with the UE according to the context of the UE, and sends NG2 interface message to the radio access network, wherein the NG2 interface message comprises SM message 4 and the connection identifier.
S606: after receiving the NG2 interface message, the radio access network sends an RRC message to the UE, where the RRC message may include SM message 4 and the connection identifier.
in some embodiments, in the PDU session, after the MM functional entity allocates the connection identifier, or each time an SM message related to a certain connection identifier is received (for example, an NG2 interface message carrying the connection identifier is received, or a message carrying the connection identifier is received from the SM functional entity), a timer corresponding to the connection identifier is started. If the SM message is received and the connection identifier for routing the SM message is the connection identifier corresponding to the timer before the timer is overtime, resetting the timer; if the timer is overtime, deleting the mapping relation information associated with the connection identifier according to the connection identifier corresponding to the timer.
the above-described procedure shown in fig. 6 is also applicable to a PDU session release procedure initiated by the UE. In some embodiments, in the PDU session release process, the SM functional entity in S604 may carry indication information in the reply message, where the indication information is used to instruct the MM functional entity to delete the mapping relationship information associated with the connection identifier carried in the reply message. In S605, after the MM functional entity sends the NG2 interface message, the mapping relationship information associated with the connection identifier may be deleted according to the indication information. Alternatively, after sending the NG2 interface message, the MM functional entity may wait for a set long time before deleting the mapping relationship information associated with the connection identifier. The mapping relationship information associated with the connection identifier specifically refers to mapping relationship information including the connection identifier.
fig. 7 exemplarily shows a deletion process of connection identification related information in a PDU session release procedure. As shown in fig. 7, the process may include:
s701: and the SM functional entity sends a notification message to the MM functional entity, wherein the notification message comprises the connection identifier. In this step, the SM functional entity may send the notification message to the MM functional entity after the PDU session deletion process is finished, where the connection identifier carried in the notification message is the connection identifier that needs to be deleted. In one example, only when all PDU sessions of the UE associated with a certain connection identity are released, the SM functional entity sends a notification message to the MM functional entity for notifying the MM functional entity to delete the mapping relationship information associated with the connection identity.
s702: after receiving the notification message, the MM functional entity deletes the mapping relationship information associated with the connection identifier according to the connection identifier included in the notification message. The mapping relationship information associated with the connection identifier specifically refers to mapping relationship information including the connection identifier.
in some embodiments, when an SM functional entity serving a UE changes, a connection identity may be transmitted between different SM functional entities to implement a handover of the SM functional entity.
Fig. 8 exemplarily shows a procedure for selecting a target SM functional entity for handover by an SM functional entity. Wherein, the source SM functional entity changes, and a target SM functional entity needs to be selected to process the PDU session processing operation of the source SM functional entity, and the process may include:
In S801, the source SM functional entity selects a target SM functional entity, and sends the connection identifier stored in the source SM functional entity and information of the target SM functional entity (such as an address of the target SM functional entity) to the MM functional entity through a notification message.
In S802, after receiving the notification message, the MM functional entity updates the mapping relationship between the connection identifier and the SM functional entity, which are locally stored in the MM functional entity, according to the connection identifier and the information of the target SM functional entity, which are carried in the notification message. Specifically, the MM functional entity may update the source SM functional entity in the mapping relationship information associated with the SM functional entity in the terminal context to the target functional entity.
In 803, the source SM functional entity sends its stored mapping relationship information to the target SM functional entity. The source SM functional entity may send the UE context to the target source SM functional entity (the UE context includes mapping relationship information between the PDU session and the connection identifier).
Fig. 9 exemplarily shows a process of selecting a target SM functional entity by a MM functional entity. Wherein, the source SM functional entity changes, and a target SM functional entity needs to be selected to process the PDU session processing operation of the source SM functional entity, and the process may include:
In S901, the source SM functional entity transmits a trigger message to the MM functional entity. The trigger message is used to instruct the MM functional entity to select a target SM functional entity for the source SM functional entity.
In S902, after receiving the trigger message, the MM functional entity selects a target SM functional entity for the source SM functional entity, and sends information (such as an address of the SM functional entity) of the selected target SM functional entity to the source SM functional entity.
In S903, the source SM functional entity sends the stored mapping relationship information between the PDU session and the connection identifier to the target SM functional entity. The source SM functional entity may send the UE context to the target source SM functional entity (the UE context includes mapping relationship information between the PDU session and the connection identifier).
In S904, the source SM functional entity returns an acknowledgement message to the MM functional entity. And after the MM functional entity receives the confirmation message, updating the mapping relation information between the locally stored connection identification and the SM function. Specifically, the MM functional entity may update the source SM functional entity in the mapping relationship information associated with the SM functional entity in the terminal context to the target functional entity.
in a further embodiment, the above-mentioned confirmation message may be omitted, so that the MM functional entity may update the mapping relationship information between the locally stored connection identity and the SM function after selecting the target SM functional entity for the source SM functional entity.
based on the same technical concept, the embodiment of the invention also provides MM functional entity equipment. Referring to fig. 10, the apparatus may include: the device further includes a receiving module 1001 and a processing module 1002, and further may further include a sending module 1003, where:
A receiving module 1001, configured to receive a message sent by a session management SM functional entity, where the message includes a connection identifier for routing an SM message; the processing module 1002 is configured to perform corresponding processing according to the connection identifier.
Optionally, the message sent by the SM functional entity is a first notification message. The processing module 1002 is specifically configured to: and deleting the connection identifier stored by the MM functional entity and SM functional entity information corresponding to the connection identifier according to the connection identifier.
optionally, the connection identifier is allocated by the MM functional entity, and the processing module 1002 is further configured to start a corresponding timer after the connection identifier is allocated. The processing module 1002 is specifically configured to: and after the message sent by the SM functional entity is received before the timer is overtime, resetting the timer according to the connection identifier included in the message. The processing module 1002 is further configured to: and if the timer is overtime, deleting the connection identifier stored by the MM functional entity and SM functional entity information corresponding to the connection identifier.
optionally, the message sent by the SM functional entity is a trigger message. The processing module 1002 is specifically configured to: and selecting a target SM functional entity for the SM functional entity according to the trigger message, and sending the information of the target SM functional entity to the SM functional entity.
optionally, the processing module 1002 is further configured to: and updating SM functional entity information corresponding to the connection identifier and stored by the MM functional entity into the target functional entity information.
Optionally, the processing module 1002 is specifically configured to: after receiving the confirmation message sent by the SM functional entity, updating SM functional entity information corresponding to the connection identifier and stored by the MM functional entity into the target functional entity information; the SM function entity sends the connection identifier and the corresponding session information stored by the SM function entity to the target SM function entity according to the received information of the target SM function entity.
Optionally, the message sent by the SM functional entity is a second notification message, the connection identifier included in the second notification message is the connection identifier stored by the SM functional entity, and the second notification message further includes information of the target SM functional entity selected by the SM functional entity.
optionally, the processing module 1002 is specifically configured to: and updating SM functional entity information corresponding to the connection identifier and stored by the MM functional entity to the target functional entity information according to the connection identifier and the target SM functional entity information included in the second notification message.
optionally, a message sent by the SM functional entity is a reply message, where the reply message includes a second SM message and the connection identifier, and the second SM message is a response message of the first SM message. The processing module 1002 is specifically configured to: before sending a request message to an SM functional entity, receiving the first SM message sent by a terminal through the receiving module, wherein the first SM message carries the connection identifier for routing the first SM message; inquiring a corresponding SM functional entity according to the connection identifier; and sending a request message to the queried SM function entity through a sending module, wherein the request message comprises a first SM message and the connection identifier for routing the first SM message.
in another example, the processing module 1002 is specifically configured to: before sending a request message to an SM functional entity through a sending module, receiving the first SM message sent by a terminal through a receiving module, wherein the first SM message does not carry the connection identifier for routing the first SM message; selecting an SM function entity for the first SM message, distributing the connection identification for routing the first SM message, and sending a request message to the selected SM function entity through the sending module, wherein the request message comprises the first SM message and the distributed connection identification.
Optionally, the reply message includes indication information. The processing module 1002 is further configured to: and according to the indication information, immediately deleting the connection identifier and SM functional entity information corresponding to the connection identifier or deleting the connection identifier and the SM functional entity information after the set duration.
Based on the same technical concept, the embodiment of the invention also provides SM functional entity equipment. Referring to fig. 11, the apparatus may include: the sending module 1101, the receiving module 1102, and further may include a processing module 1103, where:
A sending module 1101, configured to send a message to the mobility management MM functional entity, where the message includes a connection identifier for routing an SM message; a receiving module 1102, configured to receive a response message sent by the MM functional entity after performing corresponding processing according to the connection identifier included in the message.
optionally, a message sent by the sending module 1101 is a first notification message, where the first notification message is used to instruct the MM functional entity to delete the connection identifier stored by the MM functional entity and SM functional entity information corresponding to the connection identifier according to the connection identifier included in the first notification message.
optionally, the processing module 1103 may delete the connection identifier and the session information corresponding to the connection identifier stored by the SM functional entity after receiving the response message.
Optionally, the message is a trigger message sent by the SM functional entity, where the trigger message is used to instruct the MM functional entity to select a target SM functional entity for the SM functional entity. A processing module 1103, configured to obtain, after receiving the response message, information of a target SM functional entity carried in the response message, where the target SM functional entity is selected by the MM functional entity for the SM functional entity according to the trigger message; and sending the stored connection identifier and the session information corresponding to the connection identifier to the target SM function entity through the sending module.
optionally, the processing module 1103 may be configured to select a target SM functional entity before sending a message to the MM functional entity. Further, the sending module 1101 may be specifically configured to: and sending a second notification message to the MM function entity, wherein the connection identifier included in the second notification message is the connection identifier stored by the SM function entity, the second message also includes information of the target SM function entity, and the second notification message is used for indicating that SM function entity information corresponding to the connection identifier and stored by the MM function entity is updated to the target function entity information. Further, the sending module 1101 is further configured to: and sending the connection identifier and the corresponding session information stored by the SM functional entity to the target SM functional entity.
Based on the same technical concept, the embodiment of the invention also provides communication equipment which can realize the message transmission process realized by the MM functional entity. The communication device may include: a processor, a memory, a network interface module, and a bus interface.
The processor is responsible for managing the bus architecture and the usual processing, and the memory may store data used by the processor in performing operations. The network interface module is used for receiving and transmitting data under the control of the processor.
The bus architecture may include any number of interconnected buses and bridges, with various circuits of one or more processors, represented by a processor, and memory, represented by a memory, being linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The network interface may be a number of elements, including a transmitter and a transceiver, providing a means for communicating with various other apparatus over a transmission medium. The processor is responsible for managing the bus architecture and the usual processing, and the memory may store data used by the processor in performing operations.
the process disclosed by the embodiment of the invention can be applied to a processor or realized by the processor. In implementation, the steps of the data transmission flow may be implemented by integrated logic circuits of hardware or instructions in the form of software in a processor. The processor may be a general purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or the like that implement or perform the methods, steps, and logic blocks disclosed in embodiments of the present invention. A general purpose processor may be a microprocessor or any conventional processor or the like. The steps of a method disclosed in connection with the embodiments of the present invention may be directly implemented by a hardware processor, or may be implemented by a combination of hardware and software modules in the processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in a memory, and the processor reads information in the memory and completes the steps of the processing method of the control plane by combining hardware of the processor.
in particular, the processor, which is configured to read the program in the memory, executes the processes that can be implemented by the MM functional entity as described above.
based on the same technical concept, the embodiment of the invention also provides communication equipment which can realize the message transmission flow realized by the SM functional entity. The communication device may include: a processor, a memory, a network interface module, and a bus interface.
The processor is responsible for managing the bus architecture and the usual processing, and the memory may store data used by the processor in performing operations. The network interface module is used for receiving and transmitting data under the control of the processor.
the bus architecture may include any number of interconnected buses and bridges, with various circuits of one or more processors, represented by a processor, and memory, represented by a memory, being linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The network interface may be a number of elements, including a transmitter and a transceiver, providing a means for communicating with various other apparatus over a transmission medium. The processor is responsible for managing the bus architecture and the usual processing, and the memory may store data used by the processor in performing operations.
The process disclosed by the embodiment of the invention can be applied to a processor or realized by the processor. In implementation, the steps of the data transmission flow may be implemented by integrated logic circuits of hardware or instructions in the form of software in a processor. The processor may be a general purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or the like that implement or perform the methods, steps, and logic blocks disclosed in embodiments of the present invention. A general purpose processor may be a microprocessor or any conventional processor or the like. The steps of a method disclosed in connection with the embodiments of the present invention may be directly implemented by a hardware processor, or may be implemented by a combination of hardware and software modules in the processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in a memory, and the processor reads information in the memory and completes the steps of the processing method of the control plane by combining hardware of the processor.
In particular, the processor, which is configured to read the program in the memory, executes the procedures that can be implemented by the SM functional entity as described above.
the present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
these computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
While preferred embodiments of the present invention have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all such alterations and modifications as fall within the scope of the invention.
it will be apparent to those skilled in the art that various changes and modifications may be made in the present invention without departing from the spirit and scope of the invention. Thus, if such modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include such modifications and variations.
Claims (30)
1. A method for message transmission, comprising:
A mobility management MM functional entity receives a message sent by a session management SM functional entity, wherein the message comprises a connection identifier for routing the SM message; the MM functional entity stores the connection identifier and SM functional entity information corresponding to the connection identifier, and the SM functional entity stores the connection identifier and session information corresponding to the connection identifier;
And the MM functional entity performs corresponding processing according to the connection identifier.
2. The method of claim 1, wherein the message sent by the SM functional entity is a first notification message;
The MM functional entity performs corresponding processing according to the connection identifier, including:
And the MM functional entity deletes the connection identifier stored by the MM functional entity and SM functional entity information corresponding to the connection identifier according to the connection identifier.
3. The method of claim 1, wherein the connection identity is assigned by the MM functional entity, and wherein the MM functional entity starts a corresponding timer after assigning the connection identity;
the MM functional entity performs corresponding processing according to the connection identifier, including:
After the MM functional entity receives the message sent by the SM functional entity before the timer is overtime, the MM functional entity resets the timer according to the connection identifier included in the message;
the method further comprises the following steps:
And if the timer is overtime, the MM functional entity deletes the connection identifier stored by the MM functional entity and SM functional entity information corresponding to the connection identifier.
4. the method of claim 1, wherein the message sent by the SM functional entity is a trigger message;
The MM functional entity performs corresponding processing according to the connection identifier, including:
And the MM functional entity selects a target SM functional entity for the SM functional entity according to the trigger message and sends the information of the target SM functional entity to the SM functional entity.
5. the method of claim 4, further comprising:
and the MM functional entity updates SM functional entity information corresponding to the connection identifier and stored by the MM functional entity into the target functional entity information.
6. The method of claim 5, wherein the MM functional entity updating SM functional entity information corresponding to the connection identity stored by the MM functional entity to the target functional entity information comprises:
After receiving the confirmation message sent by the SM functional entity, the MM functional entity updates SM functional entity information corresponding to the connection identifier, which is stored by the MM functional entity, to the target functional entity information; the SM function entity sends the connection identifier and the corresponding session information stored by the SM function entity to the target SM function entity according to the received information of the target SM function entity.
7. The method of claim 1, wherein the message sent by the SM functional entity is a second notification message, the connection identifier included in the second notification message is a connection identifier stored by the SM functional entity, and the second notification message further includes information of a target SM functional entity selected by the SM functional entity.
8. The method of claim 7, wherein the MM functional entity performs corresponding processing according to the connection identifier, including:
and the MM functional entity updates SM functional entity information corresponding to the connection identifier, which is stored by the MM functional entity, into the target functional entity information according to the connection identifier and the target SM functional entity information included in the second notification message.
9. The method of claim 1, wherein the message sent by the SM functional entity is a reply message, the reply message includes a second SM message and the connection identifier, and the second SM message is a response message of the first SM message;
before the MM functional entity sends the request message to the SM functional entity, the method further includes:
the MM functional entity receives the first SM message sent by a terminal, wherein the first SM message carries the connection identifier for routing the first SM message;
The MM functional entity queries a corresponding SM functional entity according to the connection identifier;
The MM functional entity sends a request message to the inquired SM functional entity, wherein the request message comprises a first SM message and the connection identifier used for routing the first SM message;
Or before the MM functional entity sends the request message to the SM functional entity, the method further includes:
The MM functional entity receives the first SM message sent by a terminal, wherein the first SM message does not carry the connection identifier for routing the first SM message;
The MM functional entity selects an SM functional entity for the first SM message, allocates the connection identifier for routing the first SM message, and sends a request message to the selected SM functional entity, wherein the request message includes the first SM message and the allocated connection identifier.
10. The method of claim 9, wherein the reply message includes indication information;
the method further comprises the following steps:
And the MM functional entity immediately deletes the connection identifier and SM functional entity information corresponding to the connection identifier according to the indication information or deletes the connection identifier and the SM functional entity information after the set duration.
11. a method for message transmission, comprising:
The session management SM functional entity sends a message to the mobility management MM functional entity, wherein the message comprises a connection identifier for routing the SM message;
And the SM functional entity receives a response message sent by the MM functional entity after corresponding processing is carried out by the MM functional entity according to the connection identifier included in the message.
12. the method of claim 11, wherein the message sent by the SM functional entity is a first notification message, and the first notification message is used to instruct the MM functional entity to delete the connection identifier stored by the MM functional entity and SM functional entity information corresponding to the connection identifier according to the connection identifier included in the first notification message.
13. The method of claim 12, wherein after the SM functional entity receives the response message, further comprising:
and the SM functional entity deletes the connection identifier stored by the SM functional entity and the session information corresponding to the connection identifier.
14. The method of claim 11, wherein the message is a trigger message sent by the SM functional entity, the trigger message for instructing the MM functional entity to select a target SM functional entity for the SM functional entity;
After receiving the response message, the SM functional entity further includes:
acquiring information of a target SM functional entity carried in the response message, wherein the target SM functional entity is selected by the MM functional entity for the SM functional entity according to the trigger message;
and the SM functional entity sends the stored connection identifier and the session information corresponding to the connection identifier to the target SM functional entity.
15. The method of claim 11, wherein prior to the SM functional entity sending the message to the MM functional entity, further comprising:
The SM functional entity selects a target SM functional entity;
The SM functional entity sends a message to the MM functional entity, including:
The SM functional entity sends a second notification message to the MM functional entity, the connection identifier included in the second notification message is a connection identifier stored by the SM functional entity, the second notification message also includes information of the target SM functional entity, and the second notification message is used for indicating that SM functional entity information corresponding to the connection identifier and stored by the MM functional entity is updated to the target functional entity information;
The method further comprises the following steps:
And the SM functional entity sends the connection identifier and the corresponding session information stored by the SM functional entity to the target SM functional entity.
16. a mobility management, MM, functional entity device, comprising:
A receiving module, configured to receive a message sent by a session management SM functional entity, where the message includes a connection identifier for routing an SM message; the MM functional entity stores the connection identifier and SM functional entity information corresponding to the connection identifier, and the SM functional entity stores the connection identifier and session information corresponding to the connection identifier;
And the processing module is used for carrying out corresponding processing according to the connection identifier.
17. the apparatus of claim 16, wherein the message sent by the SM functional entity is a first notification message;
The processing module is specifically configured to: and deleting the connection identifier stored by the MM functional entity and SM functional entity information corresponding to the connection identifier according to the connection identifier.
18. the apparatus of claim 16, wherein the connection identifier is assigned by the MM function entity, the processing module being further configured to start a corresponding timer after assigning the connection identifier;
The processing module is specifically configured to: after receiving the message sent by the SM functional entity before the timer is overtime, resetting the timer according to the connection identifier included in the message;
the processing module is further configured to: and if the timer is overtime, deleting the connection identifier stored by the MM functional entity and SM functional entity information corresponding to the connection identifier.
19. The apparatus of claim 16, wherein the message sent by the SM functional entity is a trigger message;
the processing module is specifically configured to: and selecting a target SM functional entity for the SM functional entity according to the trigger message, and sending the information of the target SM functional entity to the SM functional entity.
20. The device of claim 19, wherein the processing module is further to: and updating SM functional entity information corresponding to the connection identifier and stored by the MM functional entity into the target functional entity information.
21. The device of claim 20, wherein the processing module is specifically configured to:
after receiving the confirmation message sent by the SM functional entity, updating SM functional entity information corresponding to the connection identifier and stored by the MM functional entity into the target functional entity information; the SM function entity sends the connection identifier and the corresponding session information stored by the SM function entity to the target SM function entity according to the received information of the target SM function entity.
22. the apparatus of claim 16, wherein the message sent by the SM functional entity is a second notification message, the connection identifier included in the second notification message is a connection identifier stored by the SM functional entity, and the second notification message further includes information of a target SM functional entity selected by the SM functional entity.
23. the device of claim 22, wherein the processing module is specifically configured to:
And updating SM functional entity information corresponding to the connection identifier and stored by the MM functional entity to the target functional entity information according to the connection identifier and the target SM functional entity information included in the second notification message.
24. the apparatus of claim 16, wherein the message sent by the SM functional entity is a reply message, the reply message includes a second SM message and the connection identifier, and the second SM message is a response message of the first SM message;
The processing module is specifically configured to: before sending a request message to an SM functional entity, receiving the first SM message sent by a terminal through the receiving module, wherein the first SM message carries the connection identifier for routing the first SM message;
inquiring a corresponding SM functional entity according to the connection identifier;
sending a request message to the queried SM function entity through a sending module, wherein the request message comprises a first SM message and the connection identifier for routing the first SM message;
Or, the processing module is specifically configured to: before sending a request message to an SM functional entity through a sending module, receiving the first SM message sent by a terminal through a receiving module, wherein the first SM message does not carry the connection identifier for routing the first SM message;
Selecting an SM function entity for the first SM message, distributing the connection identification for routing the first SM message, and sending a request message to the selected SM function entity through the sending module, wherein the request message comprises the first SM message and the distributed connection identification.
25. the apparatus of claim 24, wherein the reply message includes indication information;
The processing module is further configured to: and according to the indication information, immediately deleting the connection identifier and SM functional entity information corresponding to the connection identifier or deleting the connection identifier and the SM functional entity information after the set duration.
26. a session management, SM, functional entity device, comprising:
a sending module, configured to send a message to a mobility management MM functional entity, where the message includes a connection identifier for routing an SM message;
a receiving module, configured to receive a response message sent by the MM functional entity after performing corresponding processing according to the connection identifier included in the message.
27. The apparatus of claim 26, wherein the message sent by the sending module is a first notification message, and the first notification message is used to instruct the MM functional entity to delete the connection identifier stored by the MM functional entity and SM functional entity information corresponding to the connection identifier according to the connection identifier included in the first notification message.
28. The apparatus of claim 27, further comprising a processing module;
The processing module is used for: and after receiving the response message, deleting the connection identifier and the session information corresponding to the connection identifier, which are stored by the SM functional entity.
29. the apparatus of claim 26, wherein the message is a trigger message sent by the SM functional entity, the trigger message for instructing the MM functional entity to select a target SM functional entity for the SM functional entity;
The device further comprises a processing module, configured to obtain information of a target SM functional entity carried in the response message after receiving the response message, where the target SM functional entity is selected by the MM functional entity for the SM functional entity according to the trigger message; and sending the stored connection identifier and the session information corresponding to the connection identifier to the target SM function entity through the sending module.
30. The apparatus of claim 26, further comprising a processing module;
The processing module is used for selecting a target SM functional entity before sending a message to the MM functional entity;
The sending module is specifically configured to: sending a second notification message to the MM functional entity, where the connection identifier included in the second notification message is a connection identifier stored by the SM functional entity, the second notification message further includes information of the target SM functional entity, and the second notification message is used to instruct to update SM functional entity information corresponding to the connection identifier stored by the MM functional entity to the target functional entity information;
the sending module is further configured to: and sending the connection identifier and the corresponding session information stored by the SM functional entity to the target SM functional entity.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710014019.5A CN108617022B (en) | 2017-01-09 | 2017-01-09 | Message transmission method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710014019.5A CN108617022B (en) | 2017-01-09 | 2017-01-09 | Message transmission method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108617022A CN108617022A (en) | 2018-10-02 |
| CN108617022B true CN108617022B (en) | 2019-12-10 |
Family
ID=63658186
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710014019.5A Active CN108617022B (en) | 2017-01-09 | 2017-01-09 | Message transmission method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108617022B (en) |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102595388A (en) * | 2008-04-30 | 2012-07-18 | 华为技术有限公司 | Method and device for processing UE context |
| US9107110B2 (en) * | 2010-08-09 | 2015-08-11 | Nec Europe Ltd. | Apparatus and method for local mobility management in a clustered femtocell network |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| SG192860A1 (en) * | 2011-03-22 | 2013-09-30 | Ericsson Telefon Ab L M | Network node and method to control routing or bypassing of deployed traffic detection function nodes |
-
2017
- 2017-01-09 CN CN201710014019.5A patent/CN108617022B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102595388A (en) * | 2008-04-30 | 2012-07-18 | 华为技术有限公司 | Method and device for processing UE context |
| US9107110B2 (en) * | 2010-08-09 | 2015-08-11 | Nec Europe Ltd. | Apparatus and method for local mobility management in a clustered femtocell network |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108617022A (en) | 2018-10-02 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111918346B (en) | Communication method, device and related equipment | |
| CN107395388B (en) | Network slicing method, user equipment and base station using same | |
| CN113453301B (en) | AMF, network slice selection method and AMF | |
| CN110401972B (en) | Method, apparatus and system for routing messages in a multi-network sliced network | |
| US10716123B2 (en) | V2X message communication method and apparatus | |
| CN111918273B (en) | Network slice selection method and device | |
| CN110073686B (en) | Session activation method, device and system | |
| CN111107588B (en) | Wireless communication method, core network entity and user equipment | |
| CN109429213B (en) | Information processing method, device, equipment and computer readable storage medium | |
| JP7068492B2 (en) | Communication methods, devices, and systems | |
| EP3687259B1 (en) | Communication method and device | |
| CN111567113A (en) | Session establishment method, relay equipment selection method, relay equipment registration method and equipment | |
| KR20200097336A (en) | Method and apparatus for establishing session | |
| CN112770391A (en) | Method and device for processing mobility management | |
| CN110944361B (en) | Method and network element for load balancing | |
| CN108235376B (en) | User plane anchor point selection method and device | |
| KR20220150425A (en) | Short message service ability updating method, device and apparatus | |
| JP6829308B2 (en) | Session management method and session management network elements | |
| JP2022537643A (en) | Resource subscription method, device, server and computer storage medium | |
| CN104507054B (en) | Group member information updating method and related equipment | |
| CN109804706B (en) | Method and radio access network component for setting up a connection of a mobile terminal to a mobile radio communications network | |
| CN108617022B (en) | Message transmission method and device | |
| CN111405553B (en) | Method and device for establishing session based on 5G network | |
| CN109451543B (en) | Information processing method and device | |
| CN108476384B (en) | Data transmission method and related device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| CP01 | Change in the name or title of a patent holder |
Address after: 100191 No. 40, Haidian District, Beijing, Xueyuan Road Patentee after: CHINA ACADEMY OF TELECOMMUNICATIONS TECHNOLOGY Address before: 100191 No. 40, Haidian District, Beijing, Xueyuan Road Patentee before: CHINA ACADEMY OF TELECOMMUNICATIONS TECHNOLOGY |
|
| CP01 | Change in the name or title of a patent holder | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20210609 Address after: 100085 1st floor, building 1, yard 5, Shangdi East Road, Haidian District, Beijing Patentee after: DATANG MOBILE COMMUNICATIONS EQUIPMENT Co.,Ltd. Address before: 100191 No. 40, Haidian District, Beijing, Xueyuan Road Patentee before: CHINA ACADEMY OF TELECOMMUNICATIONS TECHNOLOGY |
|
| TR01 | Transfer of patent right |