CN115396847B

CN115396847B - Data transmission method, communication device and storage medium

Info

Publication number: CN115396847B
Application number: CN202211001054.0A
Authority: CN
Inventors: 黄倩; 黄蓉; 蔡超; 王立文; 陈杲
Original assignee: China United Network Communications Group Co Ltd
Current assignee: China United Network Communications Group Co Ltd
Priority date: 2022-08-19
Filing date: 2022-08-19
Publication date: 2024-05-03
Anticipated expiration: 2042-08-19
Also published as: CN115396847A

Abstract

The application discloses a data transmission method, a communication device and a storage medium, relates to the technical field of Internet of vehicles, and is used for guaranteeing service continuity of a vehicle-mounted terminal. The method comprises the following steps: the target SMF receives a first access request from the vehicle-mounted terminal for accessing the roaming MEC server; in the case where the user does not belong to the home subscriber and the DNN of the user of the in-vehicle terminal is a private DNN, the target SMF transmits to the roaming-destination UPF indication information of the initial-destination UPF of the visiting in-vehicle terminal, the indication information including information of the roaming-destination MEC server, the information of the roaming-destination MEC being used for data synchronization between the initial-destination MEC server and the roaming-destination MEC server of the in-vehicle terminal.

Description

Data transmission method, communication device and storage medium

Technical Field

The embodiment of the application relates to the technical field of Internet of vehicles, in particular to a data transmission method, a communication device and a storage medium.

Background

With the gradual maturity of the fifth generation (5th generation,5G) of communication technology, the internet of vehicles service is rapidly developed. At present, as the 5G network is still under construction, the Internet of vehicles service is not developed on a large scale. In actual cooperation between the current operator and the vehicle enterprise, the vehicle-mounted terminal can be uniformly connected to the central user plane function network element (user plane function, UPF) through the customized data network identifier (data network name, DNN) (the customized DNN is accessed by a private network and needs to be configured with a white list), and then the central UPF uniformly returns information to the central cloud, so that user data synchronization is completed. However, under the condition that the vehicle moves, the vehicle-mounted terminal uniformly sends information to the center UPF in real time, so that a network path for transmitting data bypasses, and the low-delay service requirement of the vehicle terminal cannot be met.

With the development of communication technologies, multi-ACESS EDGE computing (MEC) technology, which may also be referred to as multi-ACESS EDGE-closed (MEC), has become one of the important technologies supported by 5G technology. The MEC can provide services for vehicles nearby through local distribution, so that the traditional wireless access network has the conditions of service localization and close-range deployment. In some scenarios, the in-vehicle terminal needs to move from one area to another (i.e., the in-vehicle terminal roams across areas), and the MEC server serving the in-vehicle terminal device also needs to switch. However, in the case of switching the MEC server, how to ensure the continuity of the service of the vehicle-mounted terminal is a problem to be solved.

Disclosure of Invention

The application provides a data transmission method, a communication device and a storage medium, which are used for guaranteeing the continuity of service of a vehicle-mounted terminal.

In order to achieve the above purpose, the application adopts the following technical scheme:

in a first aspect, a data transmission method is provided, applied to a target session management function network element, and the method includes:

The target session management function network element receives a first access request from the target vehicle-mounted terminal, wherein the first access request is used for accessing a target mobile edge computing MEC server of an area where the target session management function network element is located, the first access request comprises DNN information of a user of the target vehicle-mounted terminal, and the DNN information is used for determining whether the user is a user of the area where the target session management function network element is located and whether DNN of the user is a special DNN;

Under the condition that the user does not belong to the area where the target session management function network element is located and the DNN of the user is a special DNN, the target session management function network element sends first indication information to the first target user plane function network element, wherein the first indication information is used for indicating the first target user plane function network element to access the initial user plane function network element of the target vehicle-mounted terminal, the first indication information comprises information of a target MEC server, and the information of the target MEC is used for data synchronization between the initial MEC server and the target MEC server of the target vehicle-mounted terminal.

In a possible implementation manner, the method further includes: the target session management function network element receives a second access request from the target vehicle-mounted terminal, wherein the second access request is used for requesting to process the first service data; the target session management function network element determines a second target user plane function network element and sends the first service data to the target MEC server through the second target user plane function network element.

In a possible implementation manner, the method further includes: the target session management function network element receives transmission path change information from the network element of the network opening function, the transmission path change information being used for indicating that a transmission path between the target vehicle-mounted terminal and the initial MEC server is changed to a transmission path between the target vehicle-mounted terminal and the target MEC server.

In a second aspect, a communication apparatus is provided, where the communication apparatus is applied to a chip or a system on a chip in a network element device of a target session management function, and may be a functional module in the network element of the target session management function for implementing the method of the first aspect or any one of the possible designs of the first aspect. The communication device may implement the functions performed by the target session management function network element in the aspects or in each possible design, where the functions may be implemented by hardware executing corresponding software. The hardware or software comprises one or more modules corresponding to the functions. Such as: the communication device includes a receiving unit and a transmitting unit.

The receiving unit is used for receiving a first access request from the target vehicle-mounted terminal, wherein the first access request is used for accessing a target mobile edge computing MEC server of an area where the target session management function network element is located, the first access request comprises DNN information of a user of the target vehicle-mounted terminal, and the DNN information is used for determining whether the user is a user of the area where the target session management function network element is located and whether DNN of the user is a special DNN;

The sending unit is configured to send, when the user does not belong to the area where the target session management function network element is located and the DNN of the user is a dedicated DNN, first indication information to the first target user plane function network element, where the first indication information is used to indicate the first target user plane function network element to access the initial user plane function network element of the target vehicle terminal, the first indication information includes information of the target MEC server, and the information of the target MEC is used for data synchronization between the initial MEC server and the target MEC server of the target vehicle terminal.

In a possible implementation manner, the apparatus further includes a determining unit; the receiving unit is further used for receiving a second access request from the target vehicle-mounted terminal, wherein the second access request comprises the information of the user; the determining unit is configured to determine a second target user plane function network element, and send, to the target MEC server, the second access request through the second target user plane function network element, where the second target user plane function network element is a user plane function network element in an area where the target session management function network element is located, the user plane function network element closest to the target vehicle-mounted terminal, where the second access request is used to request processing of the first service data.

In a possible implementation manner, the receiving unit is further configured to receive transmission path change information from the network element with the network open function, where the transmission path change information is used to instruct to change a transmission path between the target vehicle-mounted terminal and the initial MEC server to a transmission path between the target vehicle-mounted terminal and the target MEC server.

In a third aspect, a computer readable storage medium is provided, which may be a readable non-volatile storage medium, storing computer instructions or a program which, when run on a computer, cause the computer to perform the method of data transmission of the first aspect or any one of the possible designs of the aspects.

In a fourth aspect, there is provided a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of data transmission of the first aspect or any of the possible designs of the aspects.

In a fifth aspect, a communication device is provided, which may be a target session management function or a chip or a system on a chip in a target session management function, the communication device comprising one or more processors and one or more memories. The one or more memories are coupled to the one or more processors, the one or more memories being configured to store computer program code comprising computer instructions that, when executed by the one or more processors, cause the target session management function to perform the method of data transfer as described above in the first aspect or any of the possible designs of the first aspect.

In a sixth aspect, a chip system is provided, which includes a processor and a communication interface, where the chip system may be configured to implement a function performed by the target session management function in the first aspect or any of the possible designs of the first aspect, for example, the processor is configured to receive a service request from the target vehicle terminal through the communication interface. In one possible design, the chip system further includes a memory for holding program instructions and/or data. The chip system may be composed of a chip, or may include a chip and other discrete devices, without limitation.

The technical effects caused by any design manner of the second aspect to the sixth aspect may be referred to the technical effects caused by the above first aspect or any possible design of the first aspect, and will not be described in detail.

In a seventh aspect, a data transmission method is provided, applied to a target MEC server, and the method includes:

The target MEC server receives a second access request, wherein the second access request is used for requesting the MEC server to process the first service data, and the second access request comprises information of a user of the target vehicle-mounted terminal; if the user of the target vehicle-mounted terminal is not the user of the area where the MEC server is located, the target MEC server sends first request information to the network element with the network opening function, wherein the first request information is used for requesting to change the transmission path, and the changed transmission path is used for data transmission between the target vehicle-mounted terminal and the target MEC server.

In a possible implementation manner, the method further includes: the method comprises the steps that a target MEC server receives a data synchronization request of an initial MEC server from a target vehicle-mounted terminal, wherein the data synchronization request is used for requesting data synchronization with the target MEC server; after the data synchronization of the target MEC server and the original MEC server is completed, the target MEC server sends information indicating that the data synchronization is completed to a first target user plane function network element, where the first target user plane function network element is a user plane function network element determined when the target session management function network element receives an access request of the target vehicle for the first time, and the target session management function network element and the target MEC server are in the same area.

In a possible implementation manner, the method further includes: the method comprises the steps that a target MEC server receives user information from a network element with an open function, wherein the user information is information of a user in an area where the target MEC server is located; the target MEC server determines that the user of the target vehicle-mounted terminal is not a user of the area where the target MEC server is located.

In a possible implementation manner, the determining, by the target MEC server, that the user of the target vehicle-mounted terminal is not the user of the area where the target MEC server is located may specifically include:

and if the information of the user of the target vehicle-mounted terminal equipment does not belong to the information of the user in the area where the target MEC server is located, the user of the target vehicle-mounted terminal equipment is not the user in the area where the target MEC server is located.

In an eighth aspect, a communication apparatus is provided, which is applied to a chip or a system on a chip in a target MEC server device, and may be a functional module in the target MEC server for implementing the method of the seventh aspect or any of the possible designs of the seventh aspect. The communication device may implement the functions performed by the target MEC server in the aspects described above or in each possible design, which may be implemented by hardware executing corresponding software. The hardware or software comprises one or more modules corresponding to the functions. Such as: the communication device includes a receiving unit and a transmitting unit.

The receiving unit is used for receiving a second access request, the second access request is used for requesting to process the first service data, and the second access request comprises information of a user of the target vehicle-mounted terminal;

The sending unit is used for sending first request information to the network element with the network opening function if the user of the target vehicle-mounted terminal is not the user of the area where the target MEC server is located, wherein the first request information is used for requesting to change the transmission path, and the changed transmission path is used for data transmission between the target vehicle-mounted terminal and the target MEC server.

In a possible implementation manner, the receiving unit is further configured to receive a data synchronization request from an initial MEC server of the target vehicle-mounted terminal, where the data synchronization request is used to request data synchronization with the target MEC server; the sending unit is further configured to send, after the data synchronization with the initial MEC server is completed, information indicating that the data synchronization is completed to a first target user plane function network element, where the first target user plane function network element is a user plane function network element determined when the target session management function network element receives an access request of the target vehicle for the first time, and the target session management function network element and the target MEC server are in a same area.

In a possible implementation manner, the apparatus further includes a determining unit; the receiving unit is further configured to receive user information from a network element with an open function, where the user information is information of a user in an area where the target MEC server is located. The user of the target vehicle-mounted terminal is not a user of the area where the target MEC server is located, and includes:

The information of the user of the target vehicle-mounted terminal device does not belong to the information of the user in the area where the target MEC server is located.

In a ninth aspect, a computer readable storage medium is provided, which may be a readable non-volatile storage medium, the computer readable storage medium storing computer instructions or a program which, when run on a computer, cause the computer to perform the method of data transmission of the seventh aspect or any one of the possible designs of the aspects.

In a tenth aspect, there is provided a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of data transmission of the seventh aspect or any one of the possible designs of the aspects.

In an eleventh aspect, a communication device is provided, which may be a target MEC server or a chip or a system on a chip in a target MEC server, the communication device comprising one or more processors and one or more memories. The one or more memories are coupled to the one or more processors, the one or more memories being configured to store computer program code comprising computer instructions that, when executed by the one or more processors, cause the target session management function network element to perform the method of data transmission as described in the seventh aspect or any of the possible designs of the seventh aspect.

In a twelfth aspect, a chip system is provided, which includes a processor and a communication interface, where the chip system may be configured to implement a function performed by the target MEC server in any of the seventh or seventh possible designs, for example, the processor is configured to receive a service request from the target vehicle terminal through the communication interface. In one possible design, the chip system further includes a memory for holding program instructions and/or data. The chip system may be composed of a chip, or may include a chip and other discrete devices, without limitation.

The technical effects of any one of the designs of the eighth aspect to the twelfth aspect may be referred to the technical effects of any one of the possible designs of the seventh aspect or the seventh aspect, and will not be described in detail.

Drawings

Fig. 1 is a schematic structural diagram of a communication system according to an embodiment of the present application;

fig. 2 is a schematic structural diagram of another communication system according to an embodiment of the present application;

Fig. 3 is a schematic structural diagram of another communication system according to an embodiment of the present application;

Fig. 4 is a schematic structural diagram of a communication device 400 according to an embodiment of the present application;

fig. 5 is a schematic flow chart of a data transmission method according to an embodiment of the present application;

fig. 6 is a flowchart of another data transmission method according to an embodiment of the present application;

fig. 7 is a flowchart of another data transmission method according to an embodiment of the present application;

Fig. 8 is a flowchart of another data transmission method according to an embodiment of the present application;

fig. 9 is a flowchart of another data transmission method according to an embodiment of the present application;

Fig. 10 is a schematic structural diagram of another communication device 100 according to an embodiment of the present application;

fig. 11 is a schematic structural diagram of another communication device 110 according to an embodiment of the present application.

Detailed Description

Before describing the embodiments of the present application, related technical terms related to the embodiments of the present application will be explained. It should be noted that these descriptions are for easier understanding of the embodiments of the present application, and should not be construed as limiting the scope of protection of the embodiments of the present application.

MEC server: refers to an open platform near the network edge side of the object or data source, which merges the core capabilities of the network, computing, storage, and application. The MEC server can meet the key requirements of the industry on the aspects of real-time service, intelligent service, data aggregation and interoperation, safety, privacy protection and the like in the digital transformation process by providing intelligent interconnection service.

DNN: the device for low-latency traffic data access MEC UPF (shared edge node) and DNN configuration need not have an upstream classifier (uplink classifier, ULCL) function. Each communication vendor may configure a different DNN configuration. Different configured DNNs may correspond to different Domain Name Systems (DNS) NAME SYSTEM. DNS may also be used to select Virtual PRIVATE SERVER (VPS).

In one example, the naming of DNNs may be: MECJJJR. The session management function (session management function, SMF) may configure the DNN. The UPF may configure DNNs as desired.

With the continuous development of 5G communication technology, the application of the internet of vehicles service is more and more widespread, but in the actual situation at present, since the 5G network is still under construction, the internet of vehicles service is not developed on a large scale, and is actually still adopted in the cooperation of the current operator and the enterprise.

For example, as shown in fig. 1, the vehicle terminal may uniformly access the center UPF through a custom DNN (custom DNN, which needs to be configured with a white list), and transmit data (such as user information) to the center UPF. Then, after the central UPF receives the data, the data can be uniformly sent to the central cloud server, and further user information synchronization is completed. However, if the vehicle-mounted terminal moves, the user information is returned to the center UPF by the vehicle-mounted terminal, which causes the network path to bypass and cannot guarantee the privacy of the user. Meanwhile, the data transmission delay between the vehicle-mounted terminal and the central cloud server may not meet the requirement of low-delay service.

In fig. 1, a central cloud server is typically deployed in one area. When the vehicle-mounted terminals in other areas need to access the central cloud server, the information of the vehicle-mounted terminals needs to bypass the network and can be forwarded to the central cloud server, so that the data transmission delay is increased, and the requirement of low-delay service of the vehicle-mounted terminals possibly cannot be met.

In an example, to meet the requirement of low-latency services of the vehicle-mounted terminal, MEC servers may be respectively set in multiple areas, and the vehicle networking services may be deployed on MEC servers in multiple different areas. Therefore, the vehicle-mounted terminal can be accessed to the MEC server in the area nearby, the length of a transmission path is reduced, and the transmission time delay of data is reduced.

For example, as shown in a of fig. 2, the in-vehicle terminal may transmit request information for accessing the MEC server of the located area to the base station of the located location. Initially, the base station, upon receiving the request information from the vehicle terminal, may forward the request information to the session management function network element (session management function, SMF) through the authentication management function network element (authentication management function, AMF). After receiving the request information from the vehicle-mounted terminal, the SMF may select a UPF closest to the vehicle-mounted terminal from among the plurality of UPFs and forward the request information to the UPF. The UPF, upon receiving the request information from the vehicle terminal, may forward the request information to the primary MEC server. After receiving the request information, the MEC may return a response message indicating that the request information was received. In this way, the in-vehicle terminal, after receiving the response message from the local MEC server, can transmit information for requesting processing of the service data to the MEC server. That is, the transmission path between the in-vehicle terminal and the MEC server is successfully established.

The initial location in the embodiment of the present application may refer to an area where the vehicle-mounted terminal is located before the vehicle-mounted terminal crosses the area. The subsequent attribution may refer to an area where the in-vehicle terminal is located after the transregional. For example, as shown in B of fig. 2, after the in-vehicle terminal a moves from the a area to the B area, the a area may be the initial place of the in-vehicle terminal a, and the B area may be referred to as the home place of the in-vehicle terminal a.

But the vehicle-mounted terminal device needs to be switched from the MEC server in the area a to the MEC server in the area B when the vehicle-mounted terminal spans the area. In the process of switching the MEC server by the vehicle-mounted terminal, how to ensure the service continuity of the vehicle-mounted terminal becomes a problem to be solved urgently.

In view of this, an embodiment of the present application provides a data transmission method, including: when the in-vehicle terminal moves to the roaming place, a message for accessing the roaming place MEC server is transmitted to the roaming place session management function network element, the message including the subscriber DNN information. After receiving the message of the vehicle-mounted terminal, the roaming place session management function network element can determine whether the vehicle-mounted terminal is a home subscriber through the roaming place UPF. Receiving a first access request from a target vehicle-mounted terminal for accessing an MEC server of an area where a target session management function network element is located under the condition that a user is a non-local user; determining that the user is the user of the area where the session management function network element is located and the DNN of the user is the special DNN according to DNN information of the user of the target vehicle-mounted terminal included in the first access request; sending first indication information to a first target user plane function network element, and indicating the first target user plane function network element to access an initial user plane function network element of a target vehicle-mounted terminal; receiving a second access request from a target vehicle-mounted terminal; processing the first service data according to the second access request; and determining a second target user plane function network element, and sending the first service data to the target MEC server through the second target user plane function network element.

In order to clearly describe the technical solution of the embodiments of the present application, in the embodiments of the present application, the words "first", "second", etc. are used to distinguish the same item or similar items having substantially the same function and effect. For example, the first request message and the second request message are merely for distinguishing between different request messages, and are not limited in their sequencing. It will be appreciated by those of skill in the art that the words "first," "second," and the like do not limit the amount and order of execution, and that the words "first," "second," and the like do not necessarily differ.

In the present application, the words "exemplary" or "such as" are used to mean serving as an example, instance, or illustration. Any embodiment or design described herein as "exemplary" or "for example" should not be construed as preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "such as" is intended to present related concepts in a concrete fashion.

The technical scheme of the embodiment of the application can be applied to various communication systems, such as: the third generation partnership project (3rd generation partnership project,3GPP) communication system, such as the 4th generation (4th generation,4G) communication system, the long term evolution (long term evolution, LTE) system, the 5G communication system, the New Radio (NR) system, the next generation communication system, or the non-3 GPP communication system, is not limited.

The system architecture and the service scenario described in the embodiments of the present application are for more clearly describing the technical solution provided in the embodiments of the present application, and do not constitute a limitation on the technical solution provided in the embodiments of the present application, and those skilled in the art can know that, with the evolution of the network architecture and the appearance of a new service scenario, the technical solution provided in the embodiments of the present application is equally applicable to similar technical problems. The embodiment of the application is exemplified by the application of the method provided in an NR system or a 5G network.

As shown in fig. 3, fig. 3 shows a schematic structural diagram of a communication system according to an embodiment of the present application, where the communication system includes: the system comprises a vehicle-mounted terminal and a plurality of MEC servers (such as a first MEC server and a second MEC server). The areas where different MEC servers are deployed are different. For example, a first MEC server is located in a first area and a second MEC server is located in a second area. The in-vehicle terminal may access the MEC server. Thus, the vehicle-mounted terminal can access the MEC server through the network equipment and the core network equipment.

In one example, as shown in fig. 3, the in-vehicle terminal may access the first MEC server when the in-vehicle terminal is located in the first area. When the vehicle-mounted terminal is located in the second area, the vehicle-mounted terminal can access the second MEC server.

Specifically, as shown in fig. 3, the access request of the vehicle terminal in the first area may be forwarded to the first MEC server through the first network device, the first authentication management function network element, the first session management function network element, and the first user plane function network element. The access request of the vehicle terminal in the second area may be forwarded to the second MEC server through the second network device, the second authentication management function network element, the second session management function network element, and the second user plane function network element.

The first network device, the first authentication management function network element, the first session management function network element and the first user plane function network element are located in a first area. The second network device, the second authentication management function network element, the second session management function network element and the second user plane function network element are located in a second area.

In the embodiment of the application, the session management function network element is mainly used for realizing the session management functions of establishing, releasing, changing and the like of a user plane transmission logic channel, such as a protocol data unit (protocol data unit, PDU) session. The session management function network element may also be used to forward an access request from the vehicle terminal, and select a corresponding user plane function network element according to the location information of the vehicle terminal. That is, in the embodiment of the present application, a plurality of user plane function network elements may be deployed in one area.

The user plane functional network element can be used as an anchor point on a user plane transmission logic channel for completing functions of routing forwarding of user plane data, such as: and establishing a channel (namely a user plane transmission logic channel) with the terminal, forwarding the data packet between the terminal and the DN on the channel, and being responsible for filtering the data message of the terminal, forwarding the data, controlling the rate and generating charging information.

In an application scenario, when the communication system shown in fig. 3 is a 5G communication system, the authentication management function network element may be an AMF, the session management function network element may be an SMF, and the user plane function network element may be a UPF. Of course, in other scenarios, the session management function network element and the user plane function network element may also have other names, without limitation.

In one scenario, in the architecture of a 5G communication system, a MEC server may interact with a policy control function (policy control function, PCF) or a network opening function (network exposure function, NEF) of a core network control plane through an N5/N33 interface. UPF sinks to network edge deployments to reduce transmission latency. For example, as shown in fig. 3, when the vehicle-mounted terminal moves from the first area to the second area, the MEC server in the second area may continue to provide services for the vehicle-mounted terminal, thereby ensuring continuity of the services. Meanwhile, the transmission path between the vehicle-mounted terminal and the MEC server is shortened, and further the data transmission delay is reduced.

In the embodiment of the application, the network equipment is mainly used for realizing the functions of physical layer functions, resource scheduling and management, access control of terminal equipment, mobility management and the like. The network device may be a device supporting wired access or a device supporting wireless access. The access network device may be AN Access Network (AN)/radio access network (radio access network, RAN) consisting of a plurality of 5G-AN/5G-RAN nodes, for example. The 5G-AN/5G-RAN node may be: an Access Point (AP), a base station (NB), an enhanced nodeB (eNB), a next generation base station (NR nodeB, gNB), a transmission reception point (transmission reception point, TRP), a transmission point (transmission point, TP), or some other access node, etc.

It should be noted that fig. 3 is only an exemplary frame diagram, the number of network devices included in fig. 3, and names of respective devices are not limited, and other nodes may be included in addition to the functional nodes shown in fig. 3, for example, a router, a data server, and the like may be included.

In particular, the apparatus of fig. 3 may adopt the constituent structure shown in fig. 4, or may include the components shown in fig. 4. Fig. 4 is a schematic diagram of a communication device 400 according to an embodiment of the present application, where the communication device 400 may be a chip or a system on a chip in a network device. Or the communication device 400 may be a chip or a system on chip in a vehicle-mounted terminal apparatus.

As shown in fig. 4, the communication apparatus 400 includes a processor 401, a communication interface 402, and a communication line 403.

Further, the communication device 400 may also include a memory 404. The processor 401, the memory 404, and the communication interface 402 may be connected by a communication line 403.

The processor 401 is a central processing unit (central process unit, CPU), a general-purpose processor, a network processor (network processor, NP), a digital signal processor (DIGITAL SIGNAL processing, DSP), a microprocessor, a microcontroller, a programmable logic device (programmable logic device, PLD), or any combination thereof. The processor 401 may also be any other device having a processing function, such as a circuit, a device, or a software module, without limitation.

A communication interface 402 for communicating with other devices or other communication networks. The other communication network may be an ethernet, a radio access network, a wireless local area network (wireless local area networks, WLAN), etc. The communication interface 402 may be a module, a circuit, a communication interface, or any device capable of enabling communication.

Communication line 403 for transmitting information between the components included in communication device 400.

Memory 404 for storing instructions. Wherein the instructions may be computer programs.

The memory 404 may be, but is not limited to, a read-only memory (ROM) or other type of static storage device capable of storing static information and/or instructions, a random access memory (random access memory, RAM) or other type of dynamic storage device capable of storing information and/or instructions, an EEPROM, a CD-ROM (compact disc read-only memory) or other optical disk storage, an optical disk storage (including compact disk, laser disk, optical disk, digital versatile disk, blu-ray disk, etc.), a magnetic disk storage medium or other magnetic storage device, etc.

It is noted that the memory 404 may exist separately from the processor 401 or may be integrated with the processor 401. Memory 404 may be used to store instructions or program code or some data, etc. The memory 404 may be located within the communication device 400 or may be located outside the communication device 400, without limitation. The processor 401 is configured to execute instructions stored in the memory 404 to implement the method for determining antenna parameters according to the embodiment of the present application.

In one example, processor 401 may include one or more CPUs, such as CPU0 and CPU1 in fig. 4.

As an alternative implementation, the communication apparatus 400 includes a plurality of processors, for example, the processor 407 may be included in addition to the processor 401 in fig. 4.

As an alternative implementation, the communication apparatus 400 further comprises an output device 404 and an input device 406. Illustratively, the input device 406 is a keyboard, mouse, microphone, or joystick, and the output device 404 is a display, speaker (speaker), or the like.

It should be noted that the communication apparatus 400 may be a desktop computer, a portable computer, a web server, a mobile phone, a tablet computer, a wireless terminal, an embedded device, a chip system, or a device having a similar structure as in fig. 4. Furthermore, the constituent structures shown in fig. 4 do not constitute limitations on the respective apparatuses in fig. 3, and the respective apparatuses in fig. 3 may include more or less than those illustrated, or may combine some of the components, or may be arranged differently, in addition to the components shown in fig. 4.

In the embodiment of the application, the chip system can be composed of chips, and can also comprise chips and other discrete devices.

Further, actions, terms, and the like, which are referred to between embodiments of the present application, are not limited thereto. The message names of interactions between the devices or parameter names in the messages in the embodiments of the present application are just an example, and other names may be used in specific implementations without limitation.

In order to clearly describe the technical solution of the embodiments of the present application, in the embodiments of the present application, the words "first", "second", etc. are used to distinguish the same item or similar items having substantially the same function and effect. For example, the first carrier determination policy and the second carrier determination policy are merely for distinguishing between different carrier determination policies, and are not limited in order. It will be appreciated by those of skill in the art that the words "first," "second," and the like do not limit the amount and order of execution, and that the words "first," "second," and the like do not necessarily differ.

In the present application, "at least one" means one or more, and "a plurality" means two or more. "and/or", describes an association relationship of an association object, and indicates that there may be three relationships, for example, a and/or B, and may indicate: a alone, a and B together, and B alone, wherein a, B may be singular or plural. The character "/" generally indicates that the context-dependent object is an "or" relationship. "at least one of" or the like means any combination of these items, including any combination of single item(s) or plural items(s). For example, at least one (one) of a, b, or c may represent: a, b, c, a-b, a-c, b-c, or a-b-c, wherein a, b, c may be single or plural.

The carrier determining method provided in the embodiment of the present application is described below with reference to the communication system shown in fig. 1. Wherein, the actions related to the embodiments of the present application, terms and the like can be mutually referred to without limitation. The message names of interactions between the devices or parameter names in the messages in the embodiments of the present application are just an example, and other names may be used in specific implementations without limitation. The actions involved in the embodiments of the present application are just an example, and other names may be adopted in the specific implementation, for example: the "included" in the embodiments of the present application may be replaced by "carried on" or the like.

Fig. 5 provides a data transmission method according to an embodiment of the present application, as shown in fig. 5, where the method includes:

s501, the target session management function network element receives a first access request from a target vehicle-mounted terminal.

Wherein the target session management function network element may be the second authentication management function network element in fig. 3. The first access request is used for accessing a target MEC server of an area where the target session management function network element is located. The first access request comprises data network identification DNN information of a user of the target vehicle-mounted terminal. The DNN information is used for determining whether the user of the target vehicle-mounted terminal is the user of the area where the target session management function network element is located and whether the DNN of the user is a special DNN. The target MEC server is located in the same area as the target session management function network element. For example, in connection with the communication system shown in fig. 3, the target MEC server may be a second MEC server.

In an example, as shown in fig. 3, when the vehicle-mounted terminal roams from the first area to the second area, the vehicle-mounted terminal may send the first access request to the second authentication management function network element through the second network device. The second authentication management function network element forwards the first access request to the second session management function network element after receiving the first access request.

S502, when the user does not belong to the area where the target session management function network element is located and the DNN of the user is the special DNN, first indication information is sent to the first target user plane function network element. Correspondingly, the first target user plane function network element receives first indication information from the target session management function network element.

The first target user plane function network element may be the second user plane function network element in fig. 3. The DNN information of the using user may include parameters of the initial, DNN of the using user. Initially may refer to using the user's registry. The parameters of the DNN may be used to determine whether the DNN is a proprietary DNN.

The first indication information is used for indicating the first target user plane function network element to access the initial user plane function network element of the target vehicle-mounted terminal. The first indication information may include information of the target MEC server (e.g., identification information of the target MEC server). For example, an identification number (identity document, ID) may be used. The information of the target MEC may be used for data synchronization between the initial MEC server of the target in-vehicle terminal and the target MEC server. For example, in connection with fig. 3, the initial user plane function element may be the first user plane element in fig. 3. The initial MEC server may be the first MEC server in fig. 3.

For example, the initial user plane function network element may send information of the roaming MEC server to the initial MEC server after receiving the first indication information. The original MEC server may perform data synchronization with the target MEC server after receiving the information of the roaming MEC server. The process of data synchronization between the MEC server and the target MEC server initially may be referred to in the description of the subsequent embodiments, and will not be repeated here.

It should be noted that, in the embodiment of the present application, the data synchronization between the MEC server and the target MEC server may include synchronization of service data and synchronization of user information. The service data may refer to service data initially provided for the target in-vehicle terminal. The synchronized target MEC server may have the service data or may provide the service of the service data to the target vehicle-mounted terminal. The user information may include identification information of the user, and the like. In one example, the target session management function network element may determine the first target user plane function network element according to location information of a plurality of user plane function network elements in the located area. The first target user plane function network element may be a user plane function network element closest to the vehicle-mounted terminal among the plurality of target user plane function network elements.

In one example, the target session management function may determine whether the user is a user not belonging to the area where the target session management function is located according to initial location information of the user included in DNN information of the user of the target terminal. For example, if the initial location information of the user does not belong to the location area where the target session management function is located, the user is used as the user who does not belong to the area where the target session management function is located. If the initial position information of the user belongs to the position area where the target session management function is located, the user is used as the user belonging to the area where the target session management function is located.

In one example, the target session management function network element may forward the first access request to the first target user plane function network element after determining the first target user plane function network element. The first target user plane function network element may determine whether the DNN of the using user is a dedicated DNN according to the parameters of the DNN information. For example, when the parameter of the DNN of the user is a preset parameter, the DNN is a dedicated DNN. When the parameter of the DNN of the user is not a preset parameter, then the DNN is not a dedicated DNN.

The first target user plane function network element is a user plane function network element determined when the target session management function network element receives an access request of a target vehicle for the first time, and the target session management function network element and the target MEC server are in the same area.

Based on the technical solution of fig. 5, after the target session management function network element receives the access request of the vehicle-mounted terminal, when it is determined that the user of the vehicle-mounted terminal is not the user in the area where the user is located and the DNN of the user is the special DNN, the initial upc of the vehicle-mounted terminal can be accessed through the upc (i.e., roaming upc) of the area where the vehicle-mounted terminal belongs, so as to trigger data synchronization between the initial MEC server and the roaming MEC server of the vehicle-mounted terminal. Therefore, after the roaming MEC server synchronizes the data, the roaming MEC server can continuously provide data service for the vehicle-mounted terminal, and the service continuity of the vehicle-mounted terminal is ensured.

In a possible embodiment, as shown in fig. 6, an embodiment of the present application provides a data transmission method, which may further include:

s601, the target session management function network element receives a second access request from the target vehicle-mounted terminal.

Wherein the second access request includes information of the user. The second access request is for requesting processing of the first traffic data.

In one example, as shown in fig. 3, when the in-vehicle terminal roams from a first region to a second region, the in-vehicle terminal may send a second access request to a second network device.

S602, the target session management function network element determines a second target user plane function network element, and sends a second access request to the target MEC server through the second target user plane function network element. Accordingly, the target MEC server receives the second access request.

The second target user plane function network element is the user plane function network element closest to the target vehicle-mounted terminal in the area where the target session management function network element is located, and the second access request is used for requesting to process the first service data. The first target user plane functional network element and the second target user plane functional network element may be the same user plane functional network element, or may be different user plane functional network elements, which is not limited. In fig. 6, the first target user plane functional network element and the second target user plane network element are the same user plane network element.

In one example, the target session management function network element may determine the second target user plane function network element according to location information of a plurality of target user plane function network elements in the located area. The second target user plane function network element may be a user plane function network element closest to the vehicle terminal among the plurality of target user plane function network elements.

It should be noted that, in the technical solution of fig. 6, since the target MEC server has completed data synchronization with the original MEC server, the target MEC server is able to process the first service data.

Based on the technical solution of fig. 6, after receiving an access request for processing service data from the vehicle-mounted terminal, the target session management network element may determine a user plane function network element closest to the vehicle-mounted terminal, and forward service data to be processed through the user plane function network element to the target MEC server. As the target MEC server is able to handle the traffic data. Thus, the data transmission delay is reduced while the service continuity is ensured.

In a possible embodiment, as shown in fig. 7, an embodiment of the present application provides a data transmission method, which includes:

s701, the target MEC server receives the second access request.

Wherein the target MEC server may be the second MEC server in fig. 3.

S702, if the user of the target vehicle-mounted terminal is not the user of the area where the target MEC server is located, the target MEC server sends first request information to the network element with the network opening function. Correspondingly, the network element of the network opening function receives the first request information from the target MEC server.

Wherein the first request information may be used to request a change of the transmission path. The changed transmission path is used for data transmission between the target vehicle-mounted terminal and the target MEC server. For example, the transmission path before the change is a transmission path between the target in-vehicle terminal and the original MEC server. The changed transmission path is the transmission path between the target vehicle-mounted terminal and the target MEC server.

In one example, the target MEC server may accept user information from network elements of the network's open functionality. The user information may include information of users of the area where the target MEC server is located. For example, the subscriber information may include one or more of a type assignment code (type allocation code, TAC), an international mobile subscriber identity (international mobile subscriber identification number, IMSI), a data network access identifier (data network ACCESS IDENTIFIER, DNAI), a subscriber permanent identity (subscription PERMANENT IDENTIFIER, SUPI).

In one possible implementation, after the UPF initially receives the access request of the vehicle terminal, subscription information may be sent to the network element with the network open function. The subscription information is used to subscribe to user information. The network open function element may open the subscription function after receiving the subscription information. The subscription function may be used to send the user information to a MEC server of an access network open function network element. For example, the network element may send the user information of the target vehicle-mounted terminal to the first MEC server and the second MEC server. In this way, the MEC server can determine whether the user of the vehicle-mounted terminal is a user of the present area according to the user information.

In one example, if the information of the user of the target vehicle-mounted terminal is consistent with the information of the user received by the target MEC server from the network element with the open function, it is indicated that the target vehicle-mounted terminal does not belong to the user in the area where the target MEC server is located.

In yet another example, the target MEC server may also be preconfigured with user information of the area in which it is located. And if the information of the using user of the target vehicle-mounted terminal does not belong to the user information of the area, indicating that the target vehicle-mounted terminal does not belong to the user of the area where the target MEC server is located. And if the information is consistent, the target vehicle-mounted terminal is indicated to belong to the user of the area where the target MEC server is located.

Further, the network element with the network open function may perform the operation of switching the transmission path after receiving the first indication information. For example, the network open function network element may establish a transmission path with the target vehicle-mounted terminal through the target MEC server, the second target user plane function network element, the second session management function network element, and the second authentication management function network element. After the transmission path establishment is successful, the transmission path between the original MEC server and the first session management function network element may be disconnected. Based on the transmission path between the target MEC server and the target vehicle-mounted terminal, the target vehicle-mounted terminal may subsequently send a request to the target MEC server for processing the traffic data. The target MEC server may return the processing result of the service data to the target vehicle-mounted terminal.

Based on the technical solution of fig. 7, when determining that the service data of the vehicle-mounted terminal is not local traffic, the target MEC server may trigger the network element with the network open function to change the transmission path. Therefore, the vehicle-mounted terminal can use the changed transmission path to carry out data interaction with the target MEC server, and the data transmission time delay is reduced.

In a possible embodiment, the method may further comprise:

The target session management function network element receives transmission path change information from the network element of the network opening function.

The transmission path changing information is used for indicating that the transmission path between the target vehicle-mounted terminal and the original MEC server is changed to the transmission path between the target vehicle-mounted terminal and the target MEC server, or is used for indicating the changed transmission path.

In one possible embodiment, the network element of the network open function may send the transmission path change information to the network element of the target session management function after completing the operation of the transmission path switching. Correspondingly, the target session management function network element receives the transmission path change information from the network element of the network opening function.

Based on this embodiment, the target session management function network element may determine that the transmission path between the target in-vehicle terminal and the target MEC server has been established according to the transmission path change information. Therefore, when the subsequent target session management function network element receives the service data processing request from the target vehicle-mounted terminal, the request can be directly forwarded to the MEC server, and the requirement of low-delay service is met.

In a possible embodiment, as shown in fig. 8, the method may further include:

s801, the target MEC server receives a data synchronization request from an initial MEC server of the target vehicle-mounted terminal.

Wherein the data synchronization request is for requesting data synchronization with the target MEC server.

S802, after the data synchronization of the target MEC server and the original MEC server is completed, the target MEC server sends information indicating that the data synchronization is completed to the first target user plane function network element. Correspondingly, the first target user plane function network element receives information indicating that data synchronization is completed from the target MEC server.

In one example, the target MEC server may begin timing when it receives a data synchronization request from the original MEC server. When the data synchronization time exceeds the preset time, it may be determined that the data synchronization is completed. After determining that the data synchronization with the original MEC server is completed, the target MEC server may send information indicating that the data synchronization is completed to the first target user plane function network element.

Based on the technical solution of fig. 8, the target MEC server may acquire the service required by the target vehicle-mounted terminal through data synchronization with the original MEC server. Further, the target MEC server can continue to provide the service of the business data to the target in-vehicle terminal.

The method provided by the embodiment of the application is described below with reference to a specific network element.

As shown in fig. 9, a data transmission method provided in an embodiment of the present application includes:

s901, the target vehicle-mounted terminal initiates an access request to the initial SMF.

Wherein the access request may be used to request access to an initial MEC server. The access request may be, for example, a DNS access request.

In one example, the target vehicle terminal may send an access request to a network device in the area. After receiving the access request, the network device may forward to the original SMF through the AMF.

S902, the SMF initially determines a first UPF, and forwards an access request to the first UPF.

The first UPF may be the UPF closest to the target vehicle terminal.

S903, the first UPF accesses the initial MEC server and forwards the access request of the target vehicle-mounted terminal to the initial MEC server.

Based on the technical schemes of S901 to S903, the target vehicle-mounted terminal can access the initial MEC server. For example, the target in-vehicle terminal may access an application of the original MEC server.

S904, the MEC server initially sends a subscription message to the NEF.

Wherein the subscription message is used for subscribing to user information.

S905, the NEF may send the user information to the MEC servers of each area according to a preset period after receiving the subscription message from the original MEC server.

For example, the network element of the network open function may synchronize user information of a user of the currently accessed in-vehicle terminal through a moving picture expert group audio player (moving picture experts group audio player, MP 2) interface.

S906, after the target vehicle-mounted terminal moves to the roaming place, the target vehicle-mounted terminal sends a query request to the roaming place SMF at the roaming place.

Wherein the target in-vehicle terminal moving to the roaming place means that the target in-vehicle terminal moves from an area where the original MEC server is located to an area where other MEC servers (i.e., the roaming place MEC server) are located.

Wherein the query request is used to query the roaming MEC server for identification information (e.g., internet protocol (internet protocol, IP) address information).

S907, the roaming SMF determines a second UPF according to the query request.

The second UPF may be a UPF closest to the target vehicle terminal among the plurality of UPFs in the roaming place. The query request includes DNN information of the using user of the target in-vehicle terminal. The DNN information may carry/include location information and parameter information of the DNN. The location information may refer to initially located information. The parameter information of the DNN is used to identify whether the DNN is a proprietary DNN (i.e., an industry-specific custom DNN).

In one example, the roaming SMF, after determining the second UPF, may forward the query request to the second UPF. After receiving the query request, the second UPF may determine, according to the query request, whether the user of the target vehicle-mounted terminal is a local user, and whether the DNN of the user is a dedicated DNN.

If the second UPF determines that the user is a non-home user and the DNN of the user is a private DNN, a first response message may be sent to the roaming SMF. The first response message is used for indicating that the user of the target vehicle-mounted terminal is a non-local user, and the DNN of the user is a special DNN. After receiving the first response message, the roaming SMF may send a message indicating an initial UPF (i.e., a first UPF) corresponding to the access target in-vehicle terminal to the second UPF.

S908, the second UPF sends an access request to the first UPF.

Wherein the access request may include identification information of the second UPF and identification information of the roaming MEC. For example, the second UPF may send an access request to the first UPF through the N9 interface.

In one example, the second UPF may turn on the network source address translation (source network address translation, SNAT) function upon receiving a message from the roaming SMF indicating the initial UPF corresponding to the visiting target in-vehicle terminal. The SNAT function may refer to the prior art and will not be described in detail.

In yet another example, when the query request in S906 further includes service data to be processed, the access request sent by the second UPF to the first UPF may include the service data to be processed. As such, the first UPF may perform S907 after receiving the access request.

S909, the first UPF transmits the service data to be processed or the identification information of the roaming MEC server to the original MEC server.

S910, the original MEC server transmits a message for requesting a data synchronization request to the roaming MEC server.

In one example, the original MEC server may determine address information of the roaming MEC server based on the identity of the roaming MEC server and send a message requesting data synchronization to the roaming MEC server based on the address information of the roaming MEC server.

S911, the roaming MEC server performs data synchronization with the original MEC server after receiving a message for requesting data synchronization from the original MEC server.

In one example, the roaming MEC server may determine whether data synchronization is complete based on a preset time threshold. For example, if the data synchronization process between the roaming MEC server and the original MEC server exceeds the time threshold, it is determined that the data synchronization is complete.

Further, after determining that the data synchronization with the original MEC server is completed, the roaming MEC may send an indication of the completion of the data synchronization to the roaming session management function network element.

S912, the target vehicle terminal transmits the access request again to the roaming SMF.

Wherein the access request may be for requesting processing of the first service data. The access information comprises information of a user of the target vehicle-mounted terminal and first service data.

S913, the roaming SMF determines a third UPF.

The third UPF is the UPF closest to the target vehicle-mounted terminal in the roaming place. The third UPF may be the same as the second UPF or may be different from the second UPF.

S914, the roaming SMF forwards the access request to the roaming MEC server through the third UPF.

In S915, the roaming MEC server transmits information requesting to change the transmission path to the NEF when determining whether or not the first service data is non-local service data.

For example, the roaming MEC server may determine whether the user of the target vehicle-mounted terminal is a home user based on receiving the user information transmitted from the NEF. For example, if the user information in the access information is consistent with the user information from the NEF, the using user is a non-local user. In the case where the user is a non-local user, the first service data is non-local service data.

For another example, the roaming MEC server may identify both user information from the NEF as non-home users. Thus, when the access request is subsequently received, if the user information carried in the access request is consistent with the user information identified as the non-local user, the user information is determined to be the non-local user.

S916, NEF changes the transmission path.

For example, the NEF may establish a transmission path between the target in-vehicle terminal and the roaming MEC server through the PCF, the roaming SMF, and the third UPF, and disconnect the transmission path between the target in-vehicle terminal and the initial MEC server. Thus, the target vehicle-mounted terminal can access the roaming MEC server through the roaming SMF and the third UPF, and the service switching is completed.

Based on the technical scheme of fig. 9, after the target vehicle-mounted terminal moves to the roaming place, the target vehicle-mounted terminal can access the roaming place MEC server in a mode of customizing DNN, so that the requirement of low-delay service of the target vehicle-mounted terminal is met while the service continuity is ensured.

The above embodiments of the present application may be combined without contradiction.

The embodiment of the present application may divide the functional modules or functional units of the communication device according to the above method example, for example, each functional module or functional unit may be divided corresponding to each function, or two or more functions may be integrated into one processing module. The integrated modules may be implemented in hardware, or in software functional modules or functional units. The division of the modules or units in the embodiment of the present application is schematic, which is merely a logic function division, and other division manners may be implemented in practice.

In the case of dividing the respective functional modules by the respective functions, fig. 10 shows a schematic structural diagram of a communication device 100, and the communication device 100 may be a target session management functional network element or a chip applied to the target session management functional network element, and the communication device 100 may be used to perform the functions of the target session management functional network element as referred to in the above embodiments. The communication apparatus 100 shown in fig. 10 may include: a receiving unit 1001 and a transmitting unit 1002.

A receiving unit 1001, configured to receive a first access request from a target vehicle-mounted terminal, where the first access request is used to access a target mobile edge computing MEC server in an area where a target session management function network element is located, where the first access request includes DNN information of a user of the target vehicle-mounted terminal, where the DNN information is used to determine whether the user is a user in the area where the target session management function network element is located and whether a DNN of the user is a dedicated DNN;

The sending unit 1002 is configured to send, when the user does not belong to the area where the target session management function network element is located and the DNN of the user is a dedicated DNN, first indication information to the first target user plane function network element, where the first indication information is used to indicate the first target user plane function network element to access the initial user plane function network element of the target vehicle terminal, the first indication information includes information of the target MEC server, and the information of the target MEC is used for data synchronization between the initial MEC server and the target MEC server of the target vehicle terminal.

In a possible implementation manner, the apparatus further includes a determining unit; the receiving unit 1001 is further configured to receive a second access request from the target vehicle-mounted terminal, where the second access request includes information of the user; the determining unit is configured to determine a second target user plane function network element, and send, to the target MEC server, the second access request through the second target user plane function network element, where the second target user plane function network element is a user plane function network element in an area where the target session management function network element is located, the user plane function network element closest to the target vehicle-mounted terminal, where the second access request is used to request processing of the first service data.

In a possible implementation manner, the receiving unit 1001 is further configured to receive transmission path change information from a network element with an open function, where the transmission path change information is used to instruct to change a transmission path between the target vehicle terminal and the original MEC server to a transmission path between the target vehicle terminal and the target MEC server.

In a possible design, the communication device 100 shown in fig. 10 may further comprise a storage unit 1003. The storage unit 1003 is used for storing program codes and instructions.

As yet another implementation, the receiving unit 1001 in fig. 10 may be replaced by a transceiver or transceiving unit, which may integrate the functions of the communication unit 1001. The transmitting unit 1002 in fig. 10 may be replaced by a transceiver or a transceiving unit, which may integrate the functions of the communication unit 1002.

Further, when the receiving unit 1001 is replaced by a transceiver or a transceiving unit and the transmitting unit 1002 is replaced by a transceiver or a transceiving unit, the communication device 100 according to the embodiment of the present application may be the communication device shown in fig. 3.

In the case of dividing the respective functional modules by the respective functions, fig. 11 shows a schematic structural diagram of a communication device 110, and the communication device 110 may be a target MEC server device or a chip applied to the target MEC server device, and the communication device 110 may be used to perform the functions of the target MEC server as described in the above embodiments. The communication device 110 shown in fig. 11 may include: a receiving unit 1101 and a transmitting unit 1102.

A receiving unit 1101, configured to receive a second access request, where the second access request is used to request processing of the first service data, and the second access request includes information of a user of the target vehicle-mounted terminal;

And the sending unit 1102 is configured to send, if the user of the target vehicle-mounted terminal is not a user of the area where the target MEC server is located, first request information to the network element with the network open function, where the first request information is used to request to change a transmission path, and the changed transmission path is used for data transmission between the target vehicle-mounted terminal and the target MEC server.

In a possible implementation manner, the receiving unit 1101 is further configured to receive a data synchronization request from an initial MEC server of the target vehicle-mounted terminal, where the data synchronization request is used to request to perform data synchronization with the target MEC server; the sending unit 1102 is further configured to send, after completing data synchronization with the initial MEC server, information indicating that data synchronization is completed to a first target user plane function network element, where the first target user plane function network element is a user plane function network element determined when the target session management function network element receives an access request of the target vehicle for the first time, and the target session management function network element and the target MEC server are in a same area.

In a possible implementation manner, the apparatus further includes a determining unit; the receiving unit 1101 is further configured to receive user information from a network element with an open function, where the user information is information of a user in an area where the target MEC server is located; the determining unit, configured to determine that the user of the target vehicle-mounted terminal is not a user of an area where the target MEC server is located, includes:

In one possible design, the communication device 110 shown in fig. 11 may further include a storage unit 1103. The storage unit 1103 is used for storing program codes and instructions.

As yet another implementation, the receiving unit 1101 in fig. 11 may be replaced by a transceiver or a transceiving unit, which may integrate the functions of the communication unit 1101. The transmitting unit 1102 in fig. 11 may be replaced by a transceiver or a transceiving unit, which may integrate the functions of the communication unit 1102.

Further, when the receiving unit 1101 is replaced by a transceiver or a transceiving unit and the transmitting unit 1102 is replaced by a transceiver or a transceiving unit, the communication device 110 according to the embodiment of the present application may be the communication device shown in fig. 3.

The embodiment of the application also provides a computer readable storage medium. All or part of the flow in the above method embodiments may be implemented by a computer program to instruct related hardware, where the program may be stored in the above computer readable storage medium, and when the program is executed, the program may include the flow in the above method embodiments. The computer readable storage medium may be an internal storage unit of the communication device (including the data transmitting end and/or the data receiving end) of any of the foregoing embodiments, for example, a hard disk or a memory of the communication device. The computer-readable storage medium may be an external storage device of the terminal apparatus, for example, a plug-in hard disk, a smart card (SMART MEDIA CARD, SMC), a Secure Digital (SD) card, or a flash memory card (FLASH CARD) provided in the terminal apparatus. Further, the computer readable storage medium may further include both an internal storage unit and an external storage device of the communication apparatus. The computer-readable storage medium is used to store the computer program and other programs and data required by the communication device. The above-described computer-readable storage medium may also be used to temporarily store data that has been output or is to be output.

It should be noted that the terms "first" and "second" and the like in the description, the claims and the drawings of the present application are used for distinguishing between different objects and not for describing a particular sequential order. Furthermore, the terms "comprise" and "have," as well as any variations thereof, are intended to cover a non-exclusive inclusion. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those listed steps or elements but may include other steps or elements not listed or inherent to such process, method, article, or apparatus.

It should be understood that, in the present application, "at least one (item)" means one or more, "a plurality" means two or more, "at least two (items)" means two or three and three or more, "and/or" for describing an association relationship of an association object, three kinds of relationships may exist, for example, "a and/or B" may mean: only a, only B and both a and B are present, wherein a, B may be singular or plural. The character "/" generally indicates that the context-dependent object is an "or" relationship. "at least one of" or the like means any combination of these items, including any combination of single item(s) or plural items(s). For example, at least one (one) of a, b or c may represent: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", wherein a, b, c may be single or plural.

From the foregoing description of the embodiments, it will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-described division of functional modules is illustrated, and in practical application, the above-described functional allocation may be implemented by different functional modules according to needs, i.e. the internal structure of the apparatus is divided into different functional modules to implement all or part of the functions described above.

In the several embodiments provided by the present application, it should be understood that the disclosed apparatus and method may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the modules or units is merely a logical functional division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another apparatus, or some features may be omitted, or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and the parts displayed as units may be one physical unit or a plurality of physical units, may be located in one place, or may be distributed in a plurality of different places. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or each unit size may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.

The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a readable storage medium. Based on such understanding, the technical solution of the embodiments of the present application may be essentially or a part contributing to the prior art or all or part of the technical solution may be embodied in the form of a software product stored in a storage medium, including several instructions for causing a device (may be a single-chip microcomputer, a chip or the like) or a processor (processor) to perform all or part of the steps of the method described in the embodiments of the present application. And the aforementioned storage medium includes: a usb disk, a removable hard disk, a ROM, a RAM, a magnetic disk, or an optical disk, etc.

The foregoing is merely illustrative of specific embodiments of the present application, and the scope of the present application is not limited thereto, but any changes or substitutions within the technical scope of the present application should be covered by the scope of the present application. Therefore, the protection scope of the application is subject to the protection scope of the claims.

Claims

1. A data transmission method, applied to a target session management function network element, the method comprising:

receiving a first access request from a target vehicle-mounted terminal, wherein the first access request is used for accessing a target mobile edge computing MEC server of an area where a target session management function network element is located, the first access request comprises data network identification DNN information of a user of the target vehicle-mounted terminal, and the DNN information is used for determining whether the user is a user of the area where the target session management function network element is located and whether DNN of the user is a special DNN;

and under the condition that the user does not belong to the user in the area where the target session management function network element is located and the DNN of the user is a special DNN, sending first indication information to a first target user plane function network element, wherein the first indication information is used for indicating the first target user plane function network element to access an initial user plane function network element of the target vehicle-mounted terminal, the first indication information comprises information of the target MEC server, the information of the target MEC server is identification information of the target MEC server, the information of the target MEC server is used for determining address information of the target MEC server by the initial MEC server of the target vehicle-mounted terminal, and sending a data synchronization request to the target MEC server, wherein the data synchronization request is used for requesting data synchronization with the target MEC server.

2. The method according to claim 1, wherein the method further comprises:

Receiving a second access request from the target vehicle-mounted terminal, wherein the second access request comprises information of the user;

Determining a second target user plane function network element, and sending the second access request to the target MEC server through the second target user plane function network element, wherein the second target user plane function network element is a user plane function network element closest to the target vehicle-mounted terminal in an area where the target session management function network element is located, and the second access request is used for requesting to process the first service data.

3. The method according to claim 1 or 2, characterized in that the method further comprises:

and receiving transmission path changing information from a network element with a network opening function, wherein the transmission path changing information is used for indicating that a transmission path between the target vehicle-mounted terminal and the initial MEC server is changed into a transmission path between the target vehicle-mounted terminal and the target MEC server.

4. A data transmission method, applied to a target MEC server, comprising:

Receiving a data synchronization request sent by an initial MEC server of a target vehicle-mounted terminal, wherein the data synchronization request is sent by the initial MEC server of the target vehicle-mounted terminal based on address information of the target MEC server, the address information of the target MEC server is determined by the initial MEC server of the target vehicle-mounted terminal based on information of the target MEC server, the information of the target MEC server is identification information of the target MEC server, and the data synchronization request is used for requesting data synchronization with the target MEC server;

receiving a second access request, wherein the second access request is used for requesting to process the first service data, and the second access request comprises information of a user of the target vehicle-mounted terminal;

If the user of the target vehicle-mounted terminal is not the user of the area where the target MEC server is located, sending first request information to a network element with a network opening function, wherein the first request information is used for requesting to change a transmission path, and the changed transmission path is used for data transmission between the target vehicle-mounted terminal and the target MEC server.

5. The method according to claim 4, wherein the method further comprises:

After the data synchronization with the initial MEC server is completed, information indicating that the data synchronization is completed is sent to a first target user plane function network element, wherein the first target user plane function network element is a user plane function network element determined when a target session management function network element receives an access request of the target vehicle-mounted terminal for the first time, and the target session management function network element and the target MEC server are in the same area.

6. The method according to claim 4 or 5, characterized in that the method further comprises:

Receiving user information from the network element with the network opening function, wherein the user information is information of users in an area where the target MEC server is located;

The user of the target vehicle-mounted terminal is not a user of the area where the target MEC server is located, including:

The information of the user of the target vehicle-mounted terminal equipment does not belong to the information of the user in the area where the target MEC server is located.

7. A communication device for application to a target session management function network element, the device comprising:

A receiving unit, configured to receive a first access request from a target vehicle-mounted terminal, where the first access request is used to access a target mobile edge computing MEC server in an area where the target session management function network element is located, where the first access request includes DNN information of a user of the target vehicle-mounted terminal, where the DNN information is used to determine whether the user is a user in the area where the target session management function network element is located and whether the DNN of the user is a dedicated DNN; a sending unit, configured to send, when the user does not belong to a user in an area where the target session management function network element is located and the DNN of the user is a dedicated DNN, first instruction information to a first target user plane function network element, where the first instruction information is used to instruct the first target user plane function network element to access an initial user plane function network element of the target vehicle-mounted terminal, the first instruction information includes information of the target MEC server, the information of the target MEC server is identification information of the target MEC server, the information of the target MEC server is used by the initial MEC server of the target vehicle-mounted terminal to determine address information of the target MEC server, and send a data synchronization request to the target MEC server, where the data synchronization request is used to request to perform data synchronization with the target MEC server.

8. The apparatus according to claim 7, further comprising a determination unit;

The receiving unit is further configured to receive a second access request from the target vehicle-mounted terminal, where the second access request includes information of the user;

The determining unit is configured to determine a second target user plane function network element, and send, to the target MEC server, the second access request through the second target user plane function network element, where the second target user plane function network element is a user plane function network element in an area where the target session management function network element is located, where the user plane function network element is closest to the target vehicle-mounted terminal, and the second access request is used to request processing of the first service data.

9. The apparatus according to claim 7 or 8, wherein the receiving unit is further configured to receive transmission path change information from a network element with an open function, the transmission path change information being configured to instruct to change a transmission path between the target in-vehicle terminal and the initial MEC server to a transmission path between the target in-vehicle terminal and the target MEC server.

10. A communication device for application to a target MEC server, the device comprising:

The receiving unit is used for receiving a data synchronization request sent by an initial MEC server of a target vehicle-mounted terminal, wherein the data synchronization request is sent by the initial MEC server of the target vehicle-mounted terminal based on the address information of the target MEC server, the address information of the target MEC server is determined by the initial MEC server of the target vehicle-mounted terminal based on the information of the target MEC server, the information of the target MEC server is the identification information of the target MEC server, and the data synchronization request is used for requesting the data synchronization with the target MEC server; receiving a second access request, wherein the second access request is used for requesting to process the first service data, and the second access request comprises information of a user of the target vehicle-mounted terminal;

And the sending unit is used for sending first request information to the network element with the network opening function if the user of the target vehicle-mounted terminal is not the user of the area where the target MEC server is located, wherein the first request information is used for requesting to change the transmission path, and the changed transmission path is used for data transmission between the target vehicle-mounted terminal and the target MEC server.

11. The apparatus according to claim 10, wherein the sending unit is further configured to send, after the data synchronization with the initial MEC server is completed, information indicating that the data synchronization is completed to a first target user plane function network element, where the first target user plane function network element is a user plane function network element determined when a target session management function network element receives an access request of the target vehicle-mounted terminal for the first time, and the target session management function network element is in a same area as the target MEC server.

12. The apparatus according to claim 10 or 11, wherein the receiving unit is further configured to receive user information from the network element with open function, where the user information is information of a user in an area where the target MEC server is located;

13. A computer readable storage medium having instructions stored therein which, when executed, implement the method of any of claims 1-3 or 4-6.

14. A communication device, comprising: a processor, a memory, and a communication interface; wherein the communication interface is used for the communication of the communication device and other equipment or network; the memory is configured to store one or more programs, the one or more programs comprising computer-executable instructions that, when executed by the communication device, cause the communication device to perform the method of any of claims 1-3 or any of claims 4-6.