CN101146087A

CN101146087A - A method and system for querying registered events

Info

Publication number: CN101146087A
Application number: CNA2006101535682A
Authority: CN
Inventors: 董沛影; 树贵明
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2006-09-12
Filing date: 2006-09-12
Publication date: 2008-03-19

Abstract

The invention discloses an inquiry method for registered events, which includes: (a). primitives used to acquire registered events information is set up; (b). an upper layer utilizes the primitives set up in the step (a) and acquires the registered events information on a lower layer. The simple inquiry mechanism for the registered events is simple, will not increase the realization complexity of a MIH layer and a MIH user layer and further improve the events service. The invention also discloses an inquiry system for the registered events, which includes an upper layer entity and a lower layer entity.

Description

Method and system for inquiring registered events

Technical Field

The invention relates to the technical field of media independent switching, in particular to a method and a system for inquiring registered events in a protocol.

Background

With the development of communication technology, the reality that multiple communication networks coexist in a certain area appears, and a multimode terminal device capable of simultaneously supporting communication with multiple networks is also generated along with the demand of users. Due to the difference of different network service areas and service capabilities, a user hopes that terminal equipment used by the user can realize seamless switching among different media networks, so that the continuity of the service of the user is ensured.

Fig. 1 is a system configuration diagram of a multimode terminal device in communication with a network. As shown in fig. 1, a terminal may access a home core network through four access networks (including a wireless local area network, a WiMax network, a cellular network, and an 802.3 wired connection), and a user may wish to implement seamless handover between the four access networks, thereby ensuring continuity of services of the user.

The 802.21 protocol addresses such a need and provides an architecture for implementing a media independent handover service for a multimode terminal, as shown in fig. 2. The main idea of the protocol is to add a Media Independent Handover (MIH) layer between the two layers (MAC layer) and the three layers (network layer) of the network entity protocol stack, and to provide event, command and information services for seamless handover between different media for a multimode terminal by defining interfaces with the upper and lower layers, SME and MIH entities of the same layer of the protocol stack in the layer, as shown in fig. 3.

As can be seen from fig. 3, the MIH layer is located between two and three layers, and the MIH and media independent handover User (MIH User) layer interfaces through a unified MIH Service Access Point (SAP), while the link layer interfaces with different service access points according to a protocol of the link layer. The MIH user layer comprises three or more protocol layers: an application layer, a transport layer and a network layer; the link layer may be 802.3/2, 3GPP2, 802.11, or 802.16 protocols.

In the existing draft of the 802.21 protocol, the messages sent directly from layer to layer are called primitives. In order to use the event service provided by the MIH, the MIH user layer needs to register an event concerned by itself to the MIH layer in advance, and when some event service is not needed, the corresponding event needs to be cancelled, and the primitives of the registration event and the cancellation event are as follows: MIH _ Event _ Register/MIH _ Event _ Register; similarly, in order to use the event service provided by the bottom layer, the MIH layer needs to register the concerned events to the bottom layer in advance, and when some event services are not needed, the MIH layer needs to de-register the corresponding events, and the source words of the registered events and the annotated and cancelled events are respectively as follows: link _ Event _ Register/Link _ Event _ Deregister.

The registration process currently described in the draft 802.21 protocol is shown in fig. 4. The MIH user layer firstly registers the relevant event to the MIH layer, and then the MIH layer registers the corresponding event to the lower layer; the lower layer returns the registration result to the MIH layer, and the MIH layer transfers the registration result to the upper layer. When a certain registered link layer event occurs, the link layer first notifies the MIH layer of the event, and the MIH notifies the MIH user layer that has registered the event.

The process of logging off the event service is similar to the process of registering events and will not be described here.

As described above, only primitives for event registration and deregistration are provided in the current 802.21 protocol draft. For the MIH event, because there are multiple MIH user layers, different MIH user layers may need to register and deregister different events on the MIH layer, and although different MIH user layers may memorize the registered events by storing and maintaining the events registered on the MIH layer, the implementation complexity of each MIH user layer is increased while doing so, and especially when the MIH user layers register and deregister events for many times, the MIH user layers need to constantly perform operations such as statistics, refreshing, and the like on the registered events; similarly, for link layer events, the MIH layer also needs to register and de-register different events in different link layers, and although the MIH layer can memorize the registered events by storing and maintaining the events registered in the link layers of different media, it also increases the complexity of implementing the MIH layer, and particularly when the MIH layer registers and de-registers events in multiple different media link layers for multiple times, the MIH layer needs to constantly perform statistics, refresh, and other operations on the events registered in different media link layers.

The method for acquiring the registered event information of the upper layer at the lower layer is complex, and the realization complexity of an MIH user layer and an MIH layer is greatly increased for realizing the method, so that the current event query mechanism in the 802.21 protocol is still imperfect.

Disclosure of Invention

In view of this, the present invention provides a method for querying registered events, which can simply and conveniently implement query of registered events.

The invention also provides a system for inquiring the registered event, and the system can simply and conveniently realize the inquiry of the registered event.

In order to achieve the first object, the invention adopts the following technical scheme:

a method of querying registered events, the method comprising:

a. setting a message for acquiring registration event information;

b. and the upper layer acquires the information of the registered events of the lower layer of the upper layer by using the information set in the step a.

Preferably, the setting of the message for acquiring the registration event information in step a is as follows: setting a registration event query request message and a registration event query response message;

the step b of acquiring the information of the registered events of the upper layer and the lower layer comprises the following steps:

b1, the upper layer sends a registration event inquiry request message to the lower layer;

b2, the lower layer confirms the information of the registered event according to the received registration event inquiry request message, and sends the information of the registered event to the upper layer requesting inquiry through a registration event inquiry response message.

Preferably, when the upper layer is a media independent handover MIH user layer and the lower layer is an MIH layer in step b,

the registration event query request message and the registration event query response message are set as follows:

adding new MIH layer register event inquiry request message in protocol, MIH user layer using said message to send register event inquiry request to MIH layer;

adding new MIH layer register event inquiry response message, MIH layer using said message to send register event inquiry result to MIH user layer;

the parameters of the MIH layer registration event query request message comprise entity identifiers for initiating a request and receiving a request and identifiers of communication media;

the parameters of the MIH layer registration event inquiry response message comprise a registered event list of the MIH user layer in the MIH layer.

Preferably, when the upper layer is the MIH layer and the lower layer is the link layer in step b,

adding new link layer registration event query request message in the protocol, and the MIH layer sending the registered event query request to the link layer by using the message;

adding new link layer registration event query response message, and the link layer sending the registered event query result to the MIH layer by using the message;

the parameters of the link layer registration event query response message comprise a registered event list of the MIH layer in the link layer.

the registration event query request message and the registration event query response message are set as follows: the existing message in the extended protocol is used as a registration event query request message or a registration event query response message.

Preferably, the existing messages in the extension protocol may be:

adding a parameter for a message Link _ Event _ discover.request in a protocol, wherein the parameter represents the attribute of a query Event, and when the attribute of the Event is registered, using the expanded message as a query request message of the registration Event; using a message Link _ Event _ discover.confirm in a protocol as a registration Event query response message;

the parameters of the registration event query response message comprise a registered event list of the MIH layer in the link layer.

Preferably, the existing messages in the extension protocol may be:

taking a message Link _ Event _ discover.request in a protocol as a registration Event query request message, and taking a message Link _ Event _ discover.confirm in the protocol as a registration Event query response message;

the parameters of the registration Event query response message Link _ Event _ discover.confirm include all Event lists supported by the Link layer, and identify the registration status of each Event for the MIH layer that sends the Link _ Event _ discover.request message in the list.

Preferably, the message configured to obtain the registration event information in step a may be: setting a registration event report message or a registration event query response message;

the lower layer sends a registration event report message or a registration event query response message to the upper layer periodically or after being triggered by a preset event, and the sent message carries the information of the registered event of the lower layer of the upper layer.

Preferably, the predetermined event is that the lower layer receives an event registration command or an event logout command, or the lower layer executes the event registration command or the event logout command.

Preferably, when the upper layer is an MIH user layer and the lower layer is an MIH layer in step b,

the set registration event report message or registration event query response message is:

adding new MIH layer register event report message in protocol, MIH layer using said message to send register event information to MIH user layer;

adding new MIH layer register event inquiry response message in protocol, MIH layer using said message to send register event information to MIH user layer;

the parameters of the MIH layer registration event report message comprise a registered event list of an MIH user layer on the MIH layer;

Preferably, when the upper layer is an MIH layer and the lower layer is a link layer in step b, the set registration event report message may be:

adding new link layer registration event report information in a protocol, wherein the parameters of the link layer registration event report information comprise a registered event list of an MIH layer in a link layer;

the query response message for setting the registration event is as follows:

adding a new link layer registration event query response message in a protocol, wherein the parameters of the link layer registration event query response message comprise a registered event list of an MIH layer in a link layer; or,

expanding the existing message in the protocol, and taking the expanded message as a registration event query response message, wherein the parameter of the registration event query response message carries a registered event list.

Preferably, the existing messages in the extension protocol may be:

change the content carried in the message Link _ Event _ discover. confirm parameter in the protocol, carry the registered Event list of the MIH layer at the Link layer in its parameter, or include all Event lists supported by the Link layer, and identify the registration status of each Event in the Event list for the MIH layer to receive the message.

In order to achieve the second object, the invention adopts the following technical scheme:

a system for querying registered events, the system comprising an upper entity and a lower entity;

and the upper layer entity acquires the information of the registered event of the upper layer entity in the lower layer entity from the lower layer entity by utilizing the message which is set in the protocol and is used for acquiring the information of the registered event.

Preferably, the upper layer entity is configured to send a set registration event query request message to the lower layer entity, and receive a registration event query response message returned by the lower layer entity;

and the lower layer entity is used for receiving the registration event query request message sent by the upper layer entity, confirming the information of the registered event of the upper layer entity in the lower layer entity, and sending a registration event query response message carrying the information of the registered event to the upper layer entity.

Preferably, the lower layer entity is configured to send a registration event report message or a registration event query response message carrying registered event information to the upper layer entity periodically or after being triggered by a predetermined event;

and the upper layer entity is used for receiving the registration event report or the registration event query response message sent by the lower layer entity.

Preferably, the upper layer entity is an MIH user layer, and the lower layer entity is an MIH layer; or,

the upper layer entity is an MIH layer, and the lower layer entity is a link layer.

The technical proposal shows that the invention realizes the inquiry of the upper layer to the registration event of the lower layer by the message in the extended protocol, the inquiry mechanism of the registered event is simple, the realization complexity of an MIH layer and an MIH user layer can not be increased, and the mechanism of the event service is further improved.

Drawings

Fig. 1 is a system configuration diagram of a multimode terminal device in communication with a network.

Fig. 2 is an architecture diagram of a multimode terminal implementing a media independent handover service.

Fig. 3 is a schematic diagram of a multimode terminal providing event, command and information services for seamless handover between different media.

Fig. 4 is a registration process currently described in the draft 802.21 protocol.

FIG. 5 is a flowchart of a method for querying registered events according to the present invention.

Fig. 6 is a general structure diagram of the system for querying registered events in the present invention.

Fig. 7 is a flowchart illustrating a specific method for querying registered events according to an embodiment of the present invention.

Fig. 8 is a system diagram for querying registered events according to an embodiment of the present invention.

Fig. 9 is a system structure diagram for querying registered events according to the second embodiment of the present invention.

Fig. 10 is a flowchart of a specific method for querying registered events according to a third embodiment of the present invention.

Fig. 11 is a system structure diagram for querying registered events in the third embodiment of the present invention.

Fig. 12 is a flowchart of a specific method for querying registered events in the fourth embodiment of the present invention.

Fig. 13 is a flowchart of a specific method for querying registered events according to a fifth embodiment of the present invention.

Fig. 14 is a system configuration diagram for querying registered events according to a sixth embodiment of the present invention.

Detailed Description

In order to make the objects, technical means and advantages of the present invention more apparent, embodiments of the present invention will be described below by way of example with reference to the accompanying drawings.

The basic idea of the invention is: the upper layer queries its registration events at the lower layer are implemented by extending the messages in the protocol.

FIG. 5 is a flowchart of a method for querying registered events according to the present invention. As shown in fig. 5, the method includes:

step 501, a message for acquiring registration event information is set.

In step 502, the upper layer acquires information of the event registered by the upper layer at the lower layer thereof by using the message set in step 501.

Fig. 6 is a general structure diagram of the system for querying registered events in the present invention. As shown in fig. 6, the system includes: an upper entity 601 and a lower entity 602. In the system, an upper entity 601 acquires information of an event registered in a lower entity 602 by the upper entity 601 from the lower entity 602 by using a message set in a protocol for acquiring information of the registered event.

It can be seen from the above that, the present invention sets the message for acquiring the registered event information in the 802.21 protocol, so that the upper layer in the 802.21 protocol can acquire the information of the registered event of the lower layer thereof by the set message. The mechanism for inquiring the registered event is simple, and the implementation complexity of an MIH user layer and an MIH layer is not increased.

The present invention is further illustrated by the following specific examples in order to more fully demonstrate the spirit of the invention.

In the following embodiments, 802.21 protocol is taken as an example, and the configured messages all take the form of primitives to illustrate the specific implementation of the present invention.

The first embodiment is as follows:

in this embodiment, the upper layer is an MIH user layer, and the lower layer is an MIH layer, that is, this embodiment is a specific implementation manner of a method and system for enabling an MIH user layer to query a registered event of the MIH user layer.

The implementation manner of the embodiment is as follows: in the 802.21 protocol, an MIH layer registration event query request primitive is added, in this embodiment, the primitive is an MIH _ registered event _ discover.request, and an MIH layer registration event query response primitive is added, in this embodiment, the primitive is an MIH _ registered event _ discover.confirm, and the two added primitives are applied to realize query of different MIH user layers for events registered by themselves in the MIH layer.

Specifically, the MIH layer registration event query request primitive MIH _ registered event _ discover is a primitive sent by the MIH user layer to the MIH layer, which indicates that the MIH user layer requests the MIH layer to query for an event that it has registered in the MIH layer, and the parameters carried in the primitive are shown in table 1. The information includes the identification of the entity which initiates and receives the request and the identification of the communication media which is related to the event to be inquired. In this embodiment, the identifier of the entity initiating the request is an identifier of a certain MIH user layer, and if the request is local, the parameter may be null; the entity identification of receiving the request is the identification of a certain MIH layer, if the request is local, the parameter can also be null; the identification of the communication medium includes the type of medium used by the link (e.g., 3GPP/802.11, etc.), the MAC address of the POA, and the MAC address of the mobile terminal.

Parameter name	Data type	Effective value	Description of the invention
Parameter name	Data type	Effective value	Description of the invention	SourceIdentifier	Identifier	Effective individual identification or group identification type (Any validinividualr groupidentifier)	An identification of the entity that initiated the request. The entry may be empty if the request is local. (the identifier of the request associated. this field of information left empty if the command local.)
DestinationIdentifier	Identifier	MIH LOCAL.MIH REMOTE	An identification of the requesting entity is received. The entry may be empty if the request is local. (the destination identifier of the request order. this is the identifier of the local or peer MIH Function.)	SourceIdentifier	Identifier
DestinationIdentifier	Identifier	MIH LOCAL.MIH REMOTE		LinkIdentifier	Identifier		Identification of the communication medium. (The identifier of communication media.)

TABLE 1

MIH layer registration event query response primitive MIH _ register event _ discover. confirm is a primitive that the MIH layer sends to the MIH user layer, and indicates that the MIH layer feeds back registered event information to the MIH user layer, and the parameters carried in this primitive are shown in table 2. The information includes the entity identification for initiating and receiving the request, the identification of the communication media related to the event to be inquired and the registered event list. In this embodiment, the entity identifier of the initiation request, the entity identifier of the reception request, and the identifier of the communication medium are the entity identifier of the initiation request, the entity identifier of the reception request, and the identifier of the communication medium in the corresponding MIH _ registered event _ discover _ request primitive, respectively; the registered event list returns information of the MIH user layer that initiated the request registered events at the MIH layer. I.e. the query is implemented.

Parameter name

Data type

Effective value

Description of the invention

Source Identifier	Identifier	Any effective individual or group identification (Any validinividualr group identifier)	An identification of the entity that initiated the request; the entry may be empty if the request is local. (the identifier of the request associated. this field of information left if the command is local.)
Source Identifier	Identifier			DestinationIdentifier	Identifier	MIH LOCAL.MIH REMOTE	An identification of the requesting entity is received. The entry may be empty if the request is local. (the destination identifier of the request order. this is the identifier of the local or peer MIH Function.)
LinkIdentifier			Identification of communication media (The identifier of communication media)	DestinationIdentifier	Identifier	MIH LOCAL.MIH REMOTE
LinkIdentifier				RegisteredEventList			List of registered events

TABLE 2

After adding the two primitives, a specific method flow for querying the registered event information of the MIH user layer by any MIH user layer is shown in fig. 7, and includes:

in step 701, the MIH user layer sends an MIH layer registration event query request primitive MIH _ registeredvent _ discover _ request to the MIH layer.

The MIH user layer sends MIH layer register event inquiry request primitive MIH _ RegisteredEvent _ discover to the MIH layer, the primitive carries the identification of the MIH user layer and the identification of the MIH layer to be inquired and the identification of the communication media in the parameter of the primitive, if the request is a local request, the identification parameters of the MIH user layer and the MIH layer can be null.

In step 702, the MIH layer queries the requested registration event information.

After the MIH layer receives the primitive, it inquires the registered event of MIH user layer represented by the ID of MIH user layer carried in the primitive parameter in the MIH layer, and can go to the bottom layer to inquire the corresponding event, or when it stores the corresponding event information, it directly calls out the corresponding event information.

In step 703, the MIH layer returns an MIH layer registration event query response primitive MIH _ registerevent _ discover.

In this step, the registered event list obtained by the query in step 702 is filled in a parameter of a primitive MIH _ registered event _ discover.confirm, and the primitive is sent to the MIH user layer that requests the query.

Therefore, the aim of the MIH user layer for inquiring the registered event of the MIH layer is fulfilled.

The above is a method for the MIH user layer to query the registered events in the MIH layer in this embodiment. In addition, the embodiment also provides a system for querying the registered events at the lower layer of the upper layer. Fig. 8 is a specific structural diagram of the system. In this system, the upper layer is embodied as an MIH user layer, and the lower layer is embodied as an MIH layer. As shown in fig. 8, the system includes an MIH user layer 801 and an MIH layer 802.

The MIH user layer 801 is configured to send an MIH layer registration event query request primitive MIH _ registeredvent _ discover _ request to the MIH layer 802, request a query for a registered event to the MIH layer, and receive a primitive MIH _ registeredvent _ discover _ confirm returned by the MIH layer.

The MIH layer 802 is configured to receive an MIH layer registration event query request primitive MIH _ registered event _ discover _ request sent by the MIH user layer 801, query information of a registered event according to parameters in the primitive, fill a query result, i.e., a registered event list, in parameters of a registration event query response primitive MIH _ registered event _ discover _ confirm, and return the primitive to the MIH user layer 801.

It can be seen from the above that, the method and system in this embodiment can implement the MIH user layer to query its registration event in the MIH layer in real time, and the query method is simple to implement, and does not increase the implementation complexity of the MIH user layer and MIH layer entities.

Example two:

in this embodiment, the upper layer is an MIH user layer, and the lower layer is an MIH layer, i.e., this embodiment is another specific implementation of the method and system for querying the MIH user layer for the registered events of the MIH user layer.

The implementation manner of the embodiment is as follows: setting a registration event report primitive or a registration event query response primitive in an 802.21 protocol, carrying a registered event list of an MIH user layer in the set primitive, and actively reporting the primitive to each MIH user layer.

The set registration event query response primitive may be the primitive MIH _ registered event _ discover.confirm in the first embodiment, and the parameters thereof are the same as those in the first embodiment, and thus are not described herein again; the set registration event Report primitive may be MIH _ registered event _ Report, which carries at least a parameter registered eventlist, which represents a registered event list.

When the MIH layer reports any one of the primitives to the MIH user layer, a periodic reporting mode or a predetermined event triggering mode may be used.

If the periodic reporting mode is adopted, the MIH layer automatically sends the primitive carrying the registered event to each related MIH user layer at a preset time interval.

If a predetermined event triggering mode is adopted, the predetermined event can be a command of registering or canceling from an MIH user layer, and when the command is received or the command is completely executed, the information of the registered event of the MIH user layer entity which sends the command is actively sent to the MIH user layer entity through the two primitives.

The above is a method for the MIH user layer to query the registered events in the MIH layer in this embodiment. In addition, the embodiment also provides a system for querying the registered events at the lower layer of the upper layer. Fig. 9 is a specific structural diagram of the system. In this system, the upper layer is embodied as an MIH layer, and the lower layer is embodied as a link layer. As shown in fig. 9, the system includes an MIH layer 901 and a link layer 902.

In the system, an MIH user layer 901 is used to receive a primitive carrying registered event information sent by an MIH layer 902; the MIH layer 902 is used to actively report a primitive carrying registered event information to the MIH user layer 901 periodically or after a predetermined event trigger.

By adopting the mode in the embodiment, the MIH user layer can also acquire the information of the registered event of the MIH user layer. The difference from the first embodiment is that the MIH layer of this embodiment actively reports the information of the registered event to the MIH user layer; in the first embodiment, the MIH layer sends the information of the registered event to the MIH user layer according to the request after receiving the query request from the MIH user layer.

Example three:

in this embodiment, the upper layer is an MIH layer, and the lower layer is a link layer, that is, this embodiment is a first specific implementation of a method and a system for implementing an MIH layer to query its registered events in the link layer.

The implementation manner of the embodiment is as follows: in the 802.21 protocol, a Link layer registration event query request primitive is added, in this embodiment, the primitive is a Link _ registered event discover.request, and a Link layer registration event query response primitive is added, in this embodiment, the primitive is a Link registered event discover.confirm, and the two primitives added above are applied to realize query of different MIH layers on events registered by the MIH layers.

Specifically, the Link layer registration event query request primitive Link _ registered event _ discover is a primitive sent by the MIH layer to the Link layer, which indicates that the MIH layer requests a specific Link layer to query for events that it has registered at the Link layer.

Link layer registration event query response primitive Link _ registered event _ discover. confirm is a primitive sent by the Link layer to the MIH layer, and indicates that the Link layer feeds back registered event information to the MIH layer, and parameters carried in the primitive are shown in table 3. The link layer sends the primitive carrying the event list to the MIH layer requesting query, thus realizing query.

Parameter name	Data type	Effective value of parameter	Description of parameters
Parameter name	Data type	Effective value of parameter	Description of parameters	RegisteredEventList			List of registered events

TABLE 3

After adding the two primitives, any MIH layer entity can query the information of the events registered in the corresponding link layer through the two primitives, and the specific flow of the query method is shown in fig. 10 and includes:

in step 1001, the MIH layer sends a Link layer registration event query request primitive Link _ registered event _ discover to the Link layer.

In this step, a Link _ registered event _ discover _ request primitive indicates that an MIH layer requests a corresponding Link layer to query information of a registered event.

At step 1002, the link layer confirms the registration event information requested for the query.

In step 1003, the Link layer returns a Link layer registration event query response primitive Link _ registered event _ discover.

In this step, the registered event list obtained by the query in step 1002 is filled in a parameter of a primitive Link _ registered event _ discover.confirm, and the primitive is sent to the MIH layer entity that requests the query.

Therefore, the aim of the MIH layer entity to inquire the registered event of the entity in the link layer is fulfilled.

The above is a method for the MIH layer to query the registered events in the link layer in this embodiment. In addition, the embodiment also provides a system for querying the registered events at the lower layer of the upper layer. Fig. 11 is a specific structural diagram of the system. In this system, the upper layer is embodied as an MIH layer, and the lower layer is embodied as a link layer. As shown in fig. 11, the system includes an MIH layer 1101 and a link layer 1102.

The MIH layer 1101 is configured to send a Link layer registration event query request primitive Link _ registered event _ discover to the Link layer 1102, request a registered event to the Link layer, and receive a Link layer registration event query response primitive Link _ registered event _ discover from the Link layer.

The Link layer 1102 is configured to receive a Link layer registration event query request primitive Link _ registered event _ discover.request sent by the MIH layer 1101, query information of a registered event, fill a list of registered events, which is a query result, into a parameter of a Link layer registration event query response primitive Link _ registered event discover.confirm, and return the primitive to the MIH layer 1101.

As can be seen from the above, the method and system in this embodiment can implement the MIH layer to query its registration event in the link layer in real time, and the query method is simple to implement, and does not increase the implementation complexity of the MIH layer and the link layer entity.

Example four:

in this embodiment, the upper layer is an MIH layer, and the lower layer is a link layer, that is, this embodiment is a second specific implementation manner of the method and system for implementing the query of the MIH layer for the registered events of the MIH layer in the link layer.

The implementation manner of the embodiment is as follows: the method includes the steps that parameter expansion is carried out on a Link _ Event _ discover _ request () of an existing Link Event query request primitive in an 802.21 protocol, no parameter is carried in an existing 802.21 protocol draft, and a parameter EventFilter is added to the primitive in the embodiment, namely, the primitive is expanded to the Link _ Event _ discover _ request (). The value of the parameter EventFilter can be ALL and REGISTERED.

When the parameter EventFilter in Link _ Event _ discover.request (EventFilter) takes the value of ALL, the parameter SupportedEventList returned by the response primitive Link _ Event _ discover.confirm (SupportedEventList) contains ALL events supported by the entity receiving the query request, namely the original meaning and response mode of the Link _ Event _ discover.request () primitive; when the parameter EventFilter in Link _ Event _ discover.request (EventFilter) is taken as register, the Link Event query request primitive Link _ Event _ discover.request is a register Event query request primitive, the response primitive Link _ Event _ discover.confirm (SupportedEventList) is a register Event query response primitive, and the parameter SupportedEventList returned by the primitive contains an Event list REGISTERED by an MIH layer entity which sends the query request at the Link layer.

After extending the primitives, any MIH layer entity can query the information of the events registered in the corresponding link layer through the two primitives, and the specific flow of the query method is shown in fig. 12 and includes:

in step 1201, the MIH layer entity sends a registration Event query request primitive Link _ Event _ discover _ request (EventFilter) to the Link layer.

In step 1202, the link layer confirms the returned event information according to the received parameters of the primitive.

In this step, after receiving the Link Event _ discover _ request primitive, the Link layer determines to return all supported Event lists or the list of registered events according to the specific value of the parameter EventFilter.

In step 1203, the Link layer returns a registration Event query response primitive Link _ Event _ discover.confirm (SupportedEventList) to the MIH layer that sent the request.

In this step, the Event list obtained in step 1202 is filled into a parameter of a Link _ Event _ discover.confirm (SupportedEventList) primitive, and the primitive is returned to the MIH layer.

Thus, the purpose of MIH layer entity query event is completed. When the value of the parameter EventFilter is REGISTERED, the aim of inquiring the REGISTERED event of the MIH layer entity in the link layer is realized. The method of the present embodiment may be implemented in a system as shown in fig. 11.

Compared with the embodiment, the method in the embodiment expands the parameters on the basis of the original query request primitive, so as to achieve the purpose of sending the query request, and after receiving the expanded query request, the link layer feeds back the information of the registration event carried by the original primitive to the MIH layer. And the third embodiment realizes the purposes of sending the query request and returning the query result by adding a new primitive.

Example five:

in this embodiment, the upper layer is an MIH layer, and the lower layer is a link layer, that is, the third embodiment of the method and system for querying the link layer registered events of the MIH layer is implemented.

The implementation manner of the embodiment is as follows: the method includes the steps of performing parameter expansion on an existing Link Event query response primitive Link _ Event _ discover.confirm (SupportedEventList) in an 802.21 protocol, wherein in the existing 802.21 protocol draft, the parameter SupportedEventList of the response primitive is all Event lists supported by a return Link layer, in the embodiment, the parameter SupportedEventList of the response primitive except all Event lists supported by the feedback Link layer identifies the registration state of each Event for an MIH entity sending a query request in the list, the expanded primitive is a registration Event query response primitive, and the original Link _ Event _ discover.request primitive is a registration Event query request primitive.

After the primitive is extended, a specific flow of the method for any MIH layer entity to query the registered event information of itself in the corresponding link layer is shown in fig. 13, and includes:

in step 1301, the MIH layer entity sends a Link _ Event _ discover _ request primitive to the Link layer.

At step 1302, the link layer validates all event information supported by the link layer and the registration status of each event with respect to the entity issuing the query request.

In step 1303, the Link layer returns a primitive Link _ Event _ discover.confirm (SupportedEventList) to the MIH layer that sent the request.

In this step, a parameter of a primitive Link _ Event _ discover.confirm (SupportedEventList) carries all Event lists supported by a Link layer, and a registration state of each Event for an issued request entity is identified in the list.

Therefore, the aim of the MIH layer entity to inquire the registered event of the entity in the link layer is fulfilled. The method of the present embodiment may be implemented in a system as shown in fig. 11.

Compared with the fourth embodiment, the method in the embodiment expands the parameters on the basis of the original query response primitive, so as to achieve the purpose of carrying the registered event information. The fourth embodiment realizes the purpose of sending the request for inquiring the registered event by expanding the primitive parameter of the primitive inquiry request.

Example six:

in this embodiment, the upper layer is an MIH layer, and the lower layer is a link layer, that is, the fourth embodiment of the method and system for querying the link layer registered events of the MIH layer.

The implementation manner of the embodiment is as follows: setting a registration event report primitive or a registration event query response primitive in an 802.21 protocol, carrying a registered event list of an MIH layer in the set primitive, and actively reporting the primitive to each MIH layer.

The set registration Event query response primitive may be a newly added primitive Link _ registered Event _ discover.confirm in the third embodiment or an extended primitive Link _ Event _ discover.confirm (SupportedEventList) in the fifth embodiment, and parameters thereof are respectively the same as those in the third and fifth embodiments, and thus are not described herein again; the set registration event Report primitive may be a Link layer registration event Report primitive, which is a Link _ registered event _ Report in this embodiment and carries at least a parameter, registered event list, where the parameter represents a registered event list.

When the link layer reports any one of the primitives to the MIH layer, a periodic reporting mode or a predetermined event triggering mode may be adopted.

If the periodic reporting mode is adopted, the link layer automatically sends the primitive carrying the registered event to each related MIH user layer at intervals of a preset period of time.

If a predetermined event triggering mode is adopted, the predetermined event can be a command of registering or canceling from an MIH layer, and when the command is received or the command is completely executed, the information of the registered event of the MIH layer entity sending the command is actively sent to the MIH layer entity through the two primitives.

The above is a method for the MIH layer to query the registered events in the link layer in this embodiment. In addition, the embodiment also provides a system for querying the registered events at the lower layer of the upper layer. Fig. 14 is a specific structural diagram of the system. In this system, the upper layer is embodied as an MIH layer, and the lower layer is embodied as a link layer. As shown in fig. 14, the system includes an MIH layer 1401 and a link layer 1402.

In the system, the MIH layer 1401 is configured to receive a primitive carrying registered event information sent by the link layer 1402; the link layer 1402 is used to report the primitive carrying the registered event information to the MIH layer periodically or actively after a predetermined event trigger.

By adopting the mode in the embodiment, the MIH layer can also acquire the information of the registered event of the MIH layer in the link layer. The difference from the third to fifth embodiments is that the link layer of this embodiment actively reports the information of the registered event to the MIH layer; in the third to fifth embodiments, the link layer sends the information of the registered event to the MIH layer according to the request after receiving the query request from the MIH layer.

It can be seen from the above description of the specific embodiments that, by using the method and system of the present invention, the upper layer queries its registration events in the lower layer by extending the messages in the protocol, and this query mechanism for the registered events is simple to implement, and does not increase the implementation complexity of the MIH layer and the MIH user layer, thereby further improving the mechanism of event service.

The above description is only for the preferred embodiment of the present invention, and is not intended to limit the scope of the present invention. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A method for querying registered events, the method comprising:

a. setting a message for acquiring registration event information;

2. The method of claim 1,

the setting of the message for acquiring the registration event information in step a is as follows: setting a registration event query request message and a registration event query response message;

3. The method of claim 2 wherein when the upper layer is a Media Independent Handover (MIH) user layer and the lower layer is an MIH layer in step b,

4. The method of claim 2 wherein when the upper layer is the MIH layer and the lower layer is the link layer in step b,

5. The method of claim 2 wherein when the upper layer is the MIH layer and the lower layer is the link layer in step b,

6. The method of claim 5, wherein the existing messages in the extended protocol are:

7. The method of claim 5, wherein the existing messages in the extended protocol are:

8. The method of claim 1,

the setting of the message for acquiring the registration event information in step a is as follows: setting a registration event report message or a registration event query response message;

9. The method of claim 8, wherein the predetermined event is that a lower layer receives an event registration command or an event de-registration command, or a lower layer performs an event registration command or an event de-registration command.

10. The method of claim 8 or 9, wherein when the upper layer is an MIH user layer and the lower layer is an MIH layer in step b,

11. The method of claim 8 or 9, wherein when the upper layer is an MIH layer and the lower layer is a link layer in step b, the set registration event report message is:

the query response message for setting the registration event is as follows:

12. The method of claim 11, wherein the existing messages in the extended protocol are:

13. A system for querying registered events, the system comprising an upper entity and a lower entity;

14. The system of claim 13,

the upper layer entity is used for sending a set registration event query request message to the lower layer entity and receiving a registration event query response message returned by the lower layer entity;

15. The system of claim 13,

the lower layer entity is used for sending a registration event report message or a registration event query response message carrying registered event information to the upper layer entity periodically or after being triggered by a preset event;

16. The system of any one of claims 13 to 15,

the upper layer entity is an MIH user layer, and the lower layer entity is an MIH layer; or,