The present disclosure relates to the communications field, and in particular, to a communications device and a communication method.
A local access network (LAN) service is currently a widely used local area network service, and is mainly applied to scenarios such as enterprise offices. Currently, a LAN is deployed in a fixed wired mode. However, in a scenario in which mobile terminals perform communication through a wireless network, the mobile terminals cannot establish a LAN.
It can be learned that how to perform LAN communication based on a wireless network becomes an urgent problem to be resolved currently.
The present disclosure provides a mobile local access network device and a communication method, to resolve a problem of how to perform LAN communication based on a wireless network.
To achieve the foregoing objective, the present disclosure provides the following technical solutions.
A first aspect of the present disclosure provides a communication method, including: receiving data that is sent by a terminal through a base station, where the data includes an identifier of a receive end and to-be-sent information, the receive end and the terminal are located in a mobile local access network MLAN, and the MLAN is a local access network established based on a wireless cellular network; and sending, based on an MLAN address corresponding to the identifier of the receive end, the to-be-sent information to the receive end through the base station. It can be learned that a wireless network-based LAN can implement data communication between the terminal and the receive end without depending on a wired mode, and therefore costs can be reduced.
A second aspect of the present disclosure provides a communications device, including: a receiver and a transmitter. The receiver is configured to receive data that is sent by a terminal through a base station, where the data includes an identifier of a receive end and to-be-sent information, the receive end and the terminal are located in a mobile local access network MLAN, and the MLAN is a local access network established based on a wireless cellular network. The transmitter is configured to send, based on an MLAN address corresponding to the identifier of the receive end, the to-be-sent information to the receive end through the base station.
A third aspect of the present disclosure provides a communications device, including: a local break out module and an MLAN forwarding processing module. The local break out module is configured to receive data that is sent by a terminal through a base station, where the data includes an identifier of a receive end and to-be-sent information, the receive end and the terminal are located in a mobile local access network MLAN, and the MLAN is a local access network established based on a wireless cellular network. The MLAN forwarding processing module is configured to: query for an MLAN address corresponding to the identifier of the receive end, and send, based on the MLAN address corresponding to the identifier of the receive end, the to-be-sent information to the receive end through the base station.
In an implementation, the communications device further includes an MLAN controller and an MLAN authentication and authorization module. The MLAN controller is configured to allocate an MLAN address to the terminal. In one embodiment, the MLAN controller is further configured to allocate a tunnel to the terminal. In one embodiment, the MLAN controller is further configured to release the MLAN address and/or the tunnel. The MLAN authentication and authorization module is configured to authenticate whether the terminal is valid.
In an implementation, the communications device is disposed in an MEC module, or is disposed in a base station, or is disposed in a network as an independent network element.
In an implementation, a process of establishing the MLAN includes: receiving an identifier that is of the terminal and that is sent by the terminal through the base station; and allocating, to the terminal, an MLAN address corresponding to the identifier of the terminal.
In an implementation, the process of establishing the MLAN further includes: allocating, to the terminal, a tunnel corresponding to the identifier of the terminal; and sending information about the tunnel to the terminal through the base station.
In an implementation, the receiving data that is sent by a terminal through a base station includes: receiving the data that is encapsulated in the tunnel and that is sent by the terminal through the base station. The data is sent through the tunnel, so that data security can be improved.
In an implementation, the allocating, to the terminal, an MLAN address corresponding to the identifier of the terminal includes: if it is determined, based on the identifier of the terminal, that the terminal is valid, allocating, to the terminal, the MLAN address corresponding to the identifier of the terminal; and the allocating, to the terminal, a tunnel corresponding to the identifier of the terminal includes: if it is determined, based on the identifier of the terminal, that the terminal is valid, allocating, to the terminal, the MLAN address corresponding to the identifier of the terminal.
In an implementation, the method further includes: receiving information about a destination base station to which the terminal is handed over, where the information about the destination base station is sent by the destination base station if the terminal is handed over from a source base station to the destination base station; and updating, from the source base station to the destination base station, the base station used to send the to-be-sent information to the receive end. Therefore, it can be ensured that after the terminal is handed over, normal communication can be further performed based on an MLAN network.
A fourth aspect of the present disclosure provides a communication method, including: sending an identifier of a terminal through a base station, where the identifier of the terminal is used to obtain an MLAN address, the MLAN address is used to communicate with a device in a mobile local access network MLAN, and the MLAN is a local access network established based on a wireless cellular network; and sending data through the base station, where the data includes an identifier of a receive end and to-be-sent information, and the receive end and the terminal are located in the MLAN. It can be learned that the terminal can actively trigger obtaining of the MLAN address, to communicate with another device through the MLAN.
A fifth aspect of the present disclosure provides a terminal, including: a transmitter. The transmitter is configured to: send an identifier of the terminal through a base station, where the identifier of the terminal is used to obtain an MLAN address, the MLAN address is used to communicate with a device in a mobile local access network MLAN, and the MLAN is a local access network established based on a wireless cellular network; and send data through the base station, where the data includes an identifier of a receive end and to-be-sent information, and the receive end and the terminal are located in the MLAN.
A sixth aspect of the present disclosure provides a terminal, including: a sending module. The sending module is configured to: send an identifier of the terminal through a base station, where the identifier of the terminal is used to obtain an MLAN address, the MLAN address is used to communicate with a device in a mobile local access network MLAN, and the MLAN is a local access network established based on a wireless cellular network; and send data through the base station, where the data includes an identifier of a receive end and to-be-sent information, and the receive end and the terminal are located in the MLAN.
In an implementation, the following is further included: sending, through the base station, a request for releasing the MLAN, where the request for releasing the MLAN is used by the MLAN to release an MLAN address and/or a tunnel that correspond/corresponds to the identifier of the terminal.
A seventh aspect of the present disclosure provides a system on chip. The system on chip includes: at least one processor, a memory, an interface circuit, and a bus. The at least one processor, the memory, and the interface circuit are coupled through the bus. The system on chip may be applied to the foregoing communications device, and interact with the communications device via the interface circuit. The memory stores a program instruction. The at least one processor invokes the program instruction stored in the memory, to perform operations of the communications device. Alternatively, the system on chip may be applied to the foregoing terminal, and interact with the terminal via the interface circuit. The memory stores a program instruction. The at least one processor invokes the program instruction stored in the memory, to perform operations of the terminal.
An eighth aspect of the present disclosure provides a computer-readable storage medium. The computer-readable storage medium stores a program instruction, and when the program instruction is run on a computer, operations of the foregoing communications device or terminal are performed.
A ninth aspect of the present disclosure provides a computer program product. The computer program product includes a program instruction, and when the program instruction is invoked, operations of the foregoing communications device or terminal are performed.
To describe the technical solutions in the embodiments of the present disclosure or in the prior art more clearly, the following briefly describes the accompanying drawings required for describing the embodiments or the prior art. Apparently, the accompanying drawings in the following description show merely some embodiments of the present disclosure, and persons of ordinary skill in the art may further derive other drawings from these accompanying drawings without creative efforts.
To implement LAN communication between the mobile terminals in
As shown in
An advantage of disposing the communications device in the MEC module is that the MEC module is close to a base station in an existing network architecture, or may be disposed in the base station, and therefore, disposition of the communications device in the MEC module can reduce an MLAN-based data forwarding delay, and the MLAN device may use the BO submodule of the EPC module as the local break out module, so that costs can be reduced.
The communications device may alternatively be deployed in another device close to the base station, or may be deployed in the base station.
The following describes in detail a function of the communications device.
Operation S301: The terminal establishes an S1-U link to an EPC module.
Specifically, the terminal sends an S1-U link establishment request to the EPC module through a base station, and the EPC module sends an S1-U link establishment response to the terminal through the base station.
Operation S302: The terminal sends a tunnel establishment request to an LBO module through the base station.
The tunnel establishment request includes an identifier of the terminal. The tunnel establishment request may be generated based on a user datagram protocol (UDP).
A tunneling technology is a manner of transferring data between networks by using public network infrastructure. The data transferred through the tunneling technology may be data packets encapsulated by using different protocols. The data packets encapsulated by using other protocols are re-encrypted and encapsulated in new packet headers for sending by using a tunneling protocol. The new packet header provides routing information, so that the newly encapsulated data packet can be routed and transmitted between two endpoints of a tunnel through a public interconnection network.
A logical path over which the encapsulated data packet is transferred on a public interconnection network is referred to as a tunnel.
In this embodiment, a protocol used by the tunneling technology may be general route encapsulation (GRE) protocol or a GPRS tunneling protocol.
Operation S303: The LBO module forwards the tunnel establishment request to an MLAN controller based on an IP address of the MLAN controller.
In one embodiment, the IP address of the MLAN controller may be preconfigured on the LBO module, or may be notified by the MLAN controller to the LBO module in advance.
The IP address of the MLAN controller may alternatively be included in the tunnel establishment request, and notified by the terminal to an LBO device. Specifically, the IP address of the MLAN controller may be preconfigured on the terminal. The IP address of the MLAN controller may alternatively be preconfigured on the base station, and sent by the base station to the terminal in broadcast mode. The IP address of the MLAN controller may alternatively be obtained by the terminal by querying a network domain name. In conclusion, after obtaining the IP address of the MLAN controller, the terminal may add the IP address of the MLAN controller to the tunnel establishment request.
Operation S304: After receiving the tunnel establishment request, the MLAN controller obtains the identifier of the terminal from the tunnel establishment request, and sends an authentication request to an MLAN authentication and authorization module, where the authentication request includes the identifier of the terminal.
Operation S305: After verifying that the terminal is valid, the MLAN authentication and authorization module sends an authentication success response to the MLAN controller.
Operation S306: The MLAN controller allocates a tunnel to the terminal.
Operation S307: The MLAN controller adds, to a forwarding table, the identifier of the terminal and information about the tunnel allocated to the terminal.
Operation S308: The MLAN controller sends a tunnel establishment response to the LBO module, where the tunnel establishment response includes the information about the tunnel allocated to the terminal.
The tunnel establishment response may be generated based on the UDP protocol.
Operation S309: The LBO module sends the tunnel establishment response to the terminal through the base station, where the tunnel establishment response includes the information about the tunnel allocated to the terminal.
If the MLAN authentication and authorization module verifies that the terminal is invalid, the MLAN controller rejects establishment of the tunnel. Specifically, the tunnel establishment response includes a rejection message.
In this way, establishment of the tunnel between the terminal and an MLAN device is completed.
Operation S310: The MLAN controller allocates the IP address to the terminal in the forwarding table, and correspondingly records the IP address and the identifier of the terminal in the forwarding table. In this way, the forwarding table records the identifier of the terminal, the information about the tunnel corresponding to the identifier of the terminal, and the IP address of the terminal.
In other words, in this embodiment, in addition to the IP address that is allocated by a core network device to the terminal and that is used for wireless cellular network communication, the terminal has an IP address used for MLAN communication. The IP address is only an implementation of an MLAN address.
Specifically, the MLAN controller may negotiate with the terminal to allocate the IP address by using a dynamic host configuration protocol (DHCP).
Operation S311: The MLAN controller sends the forwarding table to an MLAN forwarding processing module.
In this way, configuration between the terminal and the MLAN is completed, and terminals may communicate with each other through the base station and the MLAN, for example, S312 to S313.
Operation S312: The terminal encapsulates data in the tunnel based on the information about the tunnel allocated by the MLAN controller, and sends the data to the MLAN device. The data includes the identifier of the terminal as a receive end of the data and to-be-sent information.
Because the tunnel includes the base station and the LBO module, a specific process in which the terminal encapsulates the data in the tunnel and sends the data to the MLAN device is as follows: The terminal sends the data to the base station, and the base station sends the data to the LBO module. In this way, transmission on the tunnel is completed, and the LBO module sends the data to the MLAN forwarding processing module.
Operation S313: The MLAN forwarding processing module queries, based on the identifier of the terminal as the receive end, the forwarding table to obtain the IP address of the terminal as the receive end and the information about the tunnel; and encapsulates the to-be-sent information in the tunnel based on the IP address and the information about the tunnel, and forwards the to-be-sent information to the terminal as the receive end.
A specific sending manner of the MLAN forwarding processing module may be unicast or multicast.
After completing an MLAN service, the terminal may delete the tunnel between the MLAN device and the base station and the terminal covered by the base station. Specifically, the following operations are included:
Operation S314: The terminal sends a request for releasing the MLAN to the LBO module through the base station.
Operation S315: The LBO module sends the request for releasing the MLAN to the MLAN controller.
Operation S316: The MLAN controller releases the tunnel allocated to the terminal.
Operation S317: The MLAN controller releases the IP address of the terminal, and deletes, from the forwarding table, the identifier of the terminal, and the IP address and the information about the tunnel that correspond to the identifier of the terminal.
Operation S318: The MLAN controller sends a terminal offline message to the MLAN authentication and authorization module.
It can be learned from the method shown in
In a wireless network, handover is a common scenario. The handover refers to a process in which a wireless connection is handed over from a source base station to a target base station after a terminal moves from coverage of one base station to coverage of another base station.
Operation S501: After a handover request and a handover response between a source base station and a destination base station are completed, the source base station sends, to the destination base station through an X2 interface, an identifier of a terminal that is handed over.
Operation S502: The destination base station sends a modify bearer request to an LBO module, where the modify bearer request includes a correspondence between the identifier of the terminal that is handed over and the destination base station.
Operation S503: The LBO module updates a tunnel corresponding to the identifier of the terminal that is handed over.
As described above, a logical path over which an encapsulated data packet is transferred on a public network is referred to as a tunnel. Therefore, if a base station covering a terminal changes from the source base station to the destination base station, the tunnel changes. The correspondence between the identifier of the terminal that is handed over and the destination base station is sent to the LBO module, and a record of the LBO module is updated to information about the tunnel corresponding to the terminal that is handed over, so that downlink data after the handover can be correctly forwarded in a subsequent data forwarding process, and an MLAN forwarding processing module is insensitive to the handover.
Operation S504: The LBO module sends an end identifier data packet to the source base station. The end identifier data packet is referred to as a first end identifier data packet in this embodiment.
Operation S505: The source base station sends the first end identifier data packet to the destination base station.
Operation S506: After the source base station receives the first end identifier data packet and a second end identifier data packet that is sent by an EPC module, or after the source base station waits for preset duration starting from release of a resource of the terminal that is handed over, the source base station releases a tunnel between the source base station and the terminal that is handed over.
Operation S507: After the destination base station receives the first end identifier data packet and the second end identifier data packet that is sent by the EPC module, or after the destination base station waits for preset duration starting from release, from the source base station, of the resource of the terminal that is handed over, the destination base station forwards the cached data.
It should be noted that this embodiment describes only a distinguishing feature between a terminal handover in an MLAN scenario and the prior art. The handover process shown in
It should be noted that the tunneling technology shown in
Therefore, as shown in
Operation S601: A terminal establishes an S1-U link to an EPC module.
Operation S602: The terminal sends an identifier of the terminal to an LBO module through a base station.
Operation S603: The LBO module sends the identifier of the terminal to an MLAN controller.
Operation S604: The MLAN controller allocates an IP address to the terminal, and correspondingly stores the identifier and the IP address of the terminal in a forwarding table.
Operation S605: The MLAN controller sends the forwarding table to an MLAN to forwarding processing module.
Operation S606: The terminal sends uplink data to the LBO module through the base station, and then the LBO module forwards received data to the MLAN forwarding processing module. The data includes the identifier of the terminal as a data receive end and to-be-sent information.
A process in which the terminal sends the uplink data to the LBO module through the base station is as follows: The terminal sends the data to the base station, and the base station forwards the data to the LBO module.
In the present disclosure, the data sent by the communications device to the terminal is first sent to the base station, and then is forwarded by the base station to the terminal.
Operation S607: The MLAN forwarding processing module queries, based on the identifier of the terminal as the receive end, the forwarding table to obtain the IP address of the terminal as the receive end, and forwards, based on the IP address, the to-be-sent information to the terminal as the receive end through the LBO module and the base station.
Operations S608 to S611 show a process of releasing the terminal, which is similar to the process of releasing the terminal in
Based on
The receiver is configured to receive data that is sent by a terminal through a base station, where the data includes an identifier of a receive end and to-be-sent information, the receive end and the terminal are located in a mobile local access network MLAN, and the MLAN is a local access network established based on a wireless cellular network. The transmitter is configured to send, based on an MLAN address corresponding to the identifier of the receive end, the to-be-sent information to the receive end through the base station. The processor is configured to allocate, to the terminal, an MLAN address corresponding to an identifier of the terminal, and may be further configured to allocate, to the terminal, a tunnel corresponding to the identifier of the terminal.
For a specific process in which the processor, the transmitter, and the receiver implement the foregoing functions and implementation of more additional functions, refer to the method embodiments. Details are not described herein again. The processor, the transmitter, and the receiver may communicate with each other through a bus.
As shown in
The communications device shown in
The transmitter is configured to: send an identifier of the terminal through a base station, where the identifier of the terminal is used to obtain an MLAN address, the MLAN address is used to communicate with a device in a mobile local access network MLAN, and the MLAN is a local access network established based on a wireless cellular network; and send data through the base station, where the data includes an identifier of a receive end and to-be-sent information, and the receive end and the terminal are located in the MLAN. In addition, the transmitter is further configured to send, through the base station, a request for releasing the MLAN, where the request for releasing the MLAN is used by the MLAN to release an MLAN address and/or a tunnel that correspond/corresponds to the identifier of the terminal.
For specific functions of the processor, the receiver, and a memory, refer to the prior art. The transmitter, the processor, the receiver, and the memory may communicate with each other through a bus.
The terminal shown in
An embodiment of the present disclosure further discloses a system on chip. The system on chip includes: at least one processor, a memory, an interface circuit, and a bus. The at least one processor, the memory, and the interface circuit are coupled through the bus.
The system on chip may be applied to the communications device shown in
Alternatively, the system on chip may be applied to the terminal shown in
An embodiment of the present disclosure further discloses a computer storage medium. The computer-readable storage medium stores a program instruction, and when the program instruction is run on a computer, operations of the communications device or the terminal shown in
An embodiment of the present disclosure further discloses a computer program product. The computer program product includes a program instruction, and when the program instruction is invoked, operations of the communications device or the terminal shown in
Terms “uplink” and “downlink” in the present disclosure are used to describe data/information transmission directions in some scenarios. For example, an “uplink” direction is a direction in which data/information is transmitted from a terminal device to a core network device, and a “downlink” direction is a direction in which the data/information is transmitted from the core network device to the terminal device. “Uplink” and “downlink” are used to describe only directions, and are not intended to limit a specific device from which data/information transmission starts or a specific device at which data/information transmission stops. A term “and/or” in this patent application describes only an association relationship for describing associated objects and represents that three relationships may exist. For example, A and/or B may represent the following three cases: Only A exists, both A and B exist, and only B exists. In addition, the character “/” in the present disclosure generally indicates an “or” relationship between the associated objects. In the present disclosure, names may be assigned to various types of objects such as messages/information/devices/network elements/systems/apparatuses/actions/operations/procedures/concepts. However, these specific names do not constitute a limitation on the related objects. The assigned names may vary with a factor such as a scenario, a context, or a usage habit. An understanding of a technical meaning of a related object should be mainly determined from a function and a technical effect that are embodied/performed in a technical solution.
In the several embodiments provided in the present disclosure, it should be understood that the disclosed system, apparatus, and method may be implemented in another manner. For example, the described apparatus embodiment is merely an example. For example, the unit division is merely logical function division and may be other division in actual implementation. For example, a plurality of units or parts may be combined or integrated into another system, or some features may be ignored or not performed. In addition, the displayed or discussed mutual couplings or direct couplings or communication connection may be implemented through some interfaces. The indirect couplings or communication connection between the apparatuses or units may be implemented in electronic, mechanical, or other forms.
The units described as separate parts may or may not be physically separate; and parts displayed as units may or may not be physical units, in other words, may be located in one position, or may be distributed on a plurality of network units. Some or all of the units may be selected based on actual requirements to achieve the objectives of the solutions of the embodiments.
In addition, functional units in the embodiments of the present disclosure may be integrated into one processing unit, or each of the units may exist alone physically, or two or more units are integrated into one unit. The integrated unit may be implemented in a form of hardware, or may be implemented in a form of a software functional unit.
When the integrated unit is implemented in the form of a software function unit and sold or used as an independent product, the integrated unit may be stored in a computer-readable storage medium. Based on such an understanding, the technical solutions of the present disclosure essentially, or the part contributing to the prior art, or all or some of the technical solutions may be implemented in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for instructing a computer device (which may be a personal computer, a server, a network device, or the like) to perform all or some of the operations of the methods described in the embodiments of the present disclosure. The foregoing storage medium includes: any medium that can store program code, such as a USB flash drive, a removable hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disc.
In conclusion, the foregoing embodiments are merely intended for describing the technical solutions of the present disclosure, but not for limiting the present disclosure. Although the present disclosure is described in detail with reference to the foregoing embodiments, persons of ordinary skill in the art should understand that they may still make modifications to the technical solutions described in the foregoing embodiments or make equivalent replacements to some technical features thereof, without departing from the spirit and scope of the technical solutions of the embodiments of the present disclosure.
This application is a continuation of International Application No. PCT/CN2017/091124, filed on Jun. 30, 2017, the disclosure of which is hereby incorporated by reference in its entirety.
| Number | Date | Country | |
|---|---|---|---|
| Parent | PCT/CN2017/091124 | Jun 2017 | US |
| Child | 16728694 | US |