CN115396847A

CN115396847A - Data transmission method, communication device, and storage medium

Info

Publication number: CN115396847A
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: 2022-11-25
Anticipated expiration: 2042-08-19
Also published as: CN115396847B

Abstract

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

Description

Data transmission method, communication device, and storage medium

Technical Field

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

Background

With the gradual maturity of the fifth generation (5g) communication technology, the internet of vehicles service is rapidly developed. At present, the 5G network is still under construction, and the Internet of vehicles service is not developed on a large scale. Actually, in cooperation between a current operator and a vehicle enterprise, a vehicle-mounted terminal may uniformly access a central user plane function network element (UPF) through a customized data network identifier (DNN) (the customized DNN is a private network access and needs to be configured with a white list), and then the central UPF uniformly returns information to a central cloud, thereby completing user data synchronization. However, when the vehicle moves, the vehicle-mounted terminal uniformly sends information to the central UPF in real time, which may cause a network path for transmitting data to detour, and may not meet the low-latency service requirement of the vehicle terminal.

With the development of communication technology, multi-access edge computing (MEC) (which may also be referred to as multi-access edge cloud (MEC)) technology has become one of the important technologies supported by the 5G technology. The MEC can provide services for vehicles nearby through local shunting, 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 area (i.e., the in-vehicle terminal roams across areas), and the MEC server providing services for the in-vehicle terminal equipment also needs to be switched. However, when the MEC server is switched, how to ensure the continuity of the service of the in-vehicle terminal becomes an urgent 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 ensuring the continuity of the service of a vehicle-mounted terminal.

In order to achieve the purpose, the following technical scheme is adopted in the application:

in a first aspect, a data transmission method is provided, where the method is 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 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 the target session management function network element is located, the first access request comprises DNN information of a user using 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 the 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 the 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 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-mounted terminal.

In a possible implementation, 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; and 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, the method further includes: and the target session management function network element receives transmission path change information from the network open function network element, wherein the transmission path change 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.

In a second aspect, a communication device is provided, which is applied to a chip or a system on chip in a target session management function network element device, and may also be a functional module in the target session management function network element for implementing the method according to the first aspect or any possible design of the first aspect. The communication device may implement the functions performed by the target session management function network element in the above aspects or possible designs, and the functions may be implemented by executing corresponding software through hardware. 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.

A receiving unit, configured to receive a first access request from a target in-vehicle 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, and the first access request includes DNN information of a user using the target in-vehicle terminal, where the DNN information is used to determine whether the user using the area where the target session management function network element is located is a user and whether the DNN using the user is a dedicated DNN;

and a sending unit, configured to send, to the first target user plane function network element, first instruction information when the user using the DNN is a dedicated DNN and the user not belonging to the area where the target session management function network element is located, 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, and the information of the target MEC is used for data synchronization between the initial MEC server of the target vehicle-mounted terminal and the target MEC server.

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, and the second access request comprises the information of the user; and the determining unit is used for 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 the user plane function network element which is 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.

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 the transmission path between the target vehicle-mounted terminal and the initial MEC server to the 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, the computer-readable storage medium storing a computer instruction or a program, which when executed on a computer, enables the computer to perform the method for data transmission according to the first aspect or any one of the above possible designs.

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 described above or of any one of the possible designs of the above aspect.

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

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

For technical effects brought by any design manner of the second aspect to the sixth aspect, reference may be made to the technical effects brought by the first aspect or any possible design of the first aspect, and details are not repeated.

In a seventh aspect, a data transmission method is provided, which is applied to a target MEC server, and 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; and 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 open function network element, 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, 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 between the target MEC server and the initial MEC server is completed, the target MEC server sends information indicating the completion of the data synchronization to a first target user plane function network element, 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.

In a possible implementation, the method further includes: the target MEC server receives user information from a network open function network element, wherein the user information is information of users 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 the 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 a user of an 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 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 also be a functional module in the target MEC server for implementing the method according to any one of the seventh aspect and any possible design of the seventh aspect. The communication means may implement the functions performed by the target MEC server in each of the above aspects or possible designs, which functions may be implemented by hardware executing the 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 processing of 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 open function network element 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 one possible implementation manner, the receiving unit is further configured to receive a data synchronization request from an initial MEC server of a target vehicle-mounted terminal, where the data synchronization request is used to request data synchronization with the target MEC server; and the sending unit is further configured to send information indicating that data synchronization is completed to a first target user plane function network element after the data synchronization with the initial MEC server is completed, 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 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.

In a possible implementation manner, the apparatus further includes a determining unit; and the receiving unit is further configured to receive user information from the network element with the network 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 the user of the region where the target MEC server is located, and the method comprises the following steps:

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.

A ninth aspect provides a computer-readable storage medium, which may be a readable non-volatile storage medium, storing a computer instruction or program, which when executed on a computer, enables the computer to perform the method for data transmission according to the seventh aspect or any one of the above aspects.

A tenth aspect provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of the seventh aspect described above or any one of the possible designs of the above aspects.

In an eleventh aspect, a communication apparatus is provided, which may be a target MEC server or a chip or system on a chip in a target MEC server, the communication apparatus including one or more processors and one or more memories. The one or more memories are coupled to the one or more processors and the one or more memories are 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 set forth in any one of the possible designs of the seventh aspect or the seventh aspect.

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

For technical effects brought by any design manner of the eighth aspect to the twelfth aspect, reference may be made to the technical effects brought by any possible design of the seventh aspect or the seventh aspect, and details are not repeated.

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 disclosure;

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

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

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

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

fig. 9 is a schematic 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 disclosure.

Detailed Description

Prior to the description of the embodiments of the present application, terms of the related art to which the embodiments of the present application relate will be explained. It should be noted that the explanation is for making the embodiments of the present application easier to understand, and should not be construed as limiting the scope of the embodiments of the present application as claimed.

An MEC server: the method is an open platform which is close to the network edge side of an object or a data source and integrates network, computing, storage and application core capabilities. The MEC server meets 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 nearby.

And (3) DNN: devices for low-latency service data access MEC UPF (shared edge node) and DNN configuration do not need to have an upstream classifier (ULCL) function. Each carrier may configure a different DNN configuration. Differently configured DNNs may correspond to different Domain Name Systems (DNS). The DNS may also be used to select a Virtual Private Server (VPS).

In one example, the DNN may be named: mecjjjr, xxx. A Session Management Function (SMF) may configure the DNN. The UPF may configure the DNN as desired.

With the continuous development of the 5G communication technology, the application of the car networking service is more and more extensive, but in the actual situation at present, as the 5G network is still under construction, the car networking service is not developed on a large scale, and is still adopted in the cooperation of the current operator and the car enterprises.

For example, as shown in fig. 1, the vehicle-mounted terminal may uniformly access the central UPF through a customized DNN (customized DNN, white list configuration is required), and transmit data (such as user information) to the central UPF. Then, after receiving the data, the central UPF may uniformly send the data to the central cloud server, thereby completing the user information synchronization. However, in the case where the in-vehicle terminal moves, if the in-vehicle terminal still returns the user information to the center UPF, a network path may be bypassed, and privacy of the user may not be guaranteed. Meanwhile, the data transmission delay between the vehicle-mounted terminal and the central cloud server may not meet the requirements of low-delay services.

In fig. 1, the 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 detour through 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 can not be met.

In one example, in order to meet the requirement of low-latency services of the vehicle-mounted terminal, MEC servers may be respectively arranged in a plurality of areas, and the vehicle networking services may be deployed on the MEC servers in a plurality of 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 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 located at the location. After receiving the request information from the vehicle-mounted terminal, the initial base station may forward the request information to a session management function network element (SMF) through an authentication management function network element (AMF). The SMF, upon receiving the request information from the in-vehicle terminal, may select a UPF closest to the in-vehicle terminal from among the plurality of UPFs, and forward the request information to the UPF. The UPF may forward the request information to the primary MEC server after receiving the request information from the in-vehicle terminal. The MEC, upon receiving the request information, may return a response message indicating receipt of the request information. In this manner, the in-vehicle terminal can transmit information for requesting processing of the service data to the MEC server after receiving the response message from the local 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 cross-zone. The subsequent home may refer to an area where the in-vehicle terminal is located from after the cross-area. For example, as shown in B of fig. 2, after the in-vehicle terminal a moves from the a zone to the B zone, the a zone may be an initial location of the in-vehicle terminal a, and the B zone may be referred to as a home location of the in-vehicle terminal a.

However, when the in-vehicle terminal crosses, the in-vehicle terminal device needs to be switched from the MEC server in the a zone to the MEC server in the B zone. In the process of switching the MEC server by the vehicle-mounted terminal, how to ensure the continuity of the service of the vehicle-mounted terminal becomes an urgent problem to be solved.

In view of this, an embodiment of the present application provides a data transmission method, including: when the vehicle-mounted terminal moves to a roaming place, sending a message for visiting the MEC server of the roaming place to a session management function network element of the roaming place, wherein the message comprises user 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 local user through the roaming place UPF. Under the condition that a user is a non-local user, 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; according to the first access request including DNN information of the user of the target vehicle-mounted terminal, determining that the user is a user in the area where the 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, and indicating the first target user plane function network element to access an initial ground user plane function network element of a target vehicle-mounted terminal; receiving a second access request from the 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 the embodiments of the present application, terms such as "first" and "second" are used to distinguish the same or similar items having substantially the same function and action. For example, the first request message and the second request message are only used for distinguishing different request messages, and the sequence order thereof is not limited. Those skilled in the art will appreciate that the terms "first," "second," and the like do not denote any order or importance, but rather the terms "first," "second," and the like do not denote any order or importance.

It is noted that, in the present application, words such as "exemplary" or "for example" are used to mean exemplary, illustrative, or descriptive. Any embodiment or design described herein as "exemplary" or "e.g.," is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, use of the word "exemplary" or "such as" is intended to present concepts related in a concrete fashion.

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

The system architecture and the service scenario described in the embodiment of the present application are for more clearly illustrating the technical solution of the embodiment of the present application, and do not form a limitation on the technical solution provided in the embodiment of the present application, and as a person of ordinary skill in the art knows that along with the evolution of the network architecture and the appearance of a new service scenario, the technical solution provided in the embodiment of the present application is also applicable to similar technical problems. In the embodiment of the present application, the method provided is applied to an NR system or a 5G network as an example.

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

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

Specifically, as shown in fig. 3, the access request of the vehicle-mounted 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-mounted 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 present application, a session management function network element is mainly used for implementing a user plane transmission logical channel, such as session management functions of establishment, release, and change of a Protocol Data Unit (PDU) session. The session management function network element can also be used for forwarding an access request from the vehicle-mounted terminal and selecting a corresponding user plane function network element according to the position information of the vehicle-mounted terminal. That is, in the embodiment of the present application, one area may be deployed with multiple user plane function network elements.

The user plane functional network element may be used as an anchor point on a user plane transmission logic channel, and is used to complete functions such as routing forwarding of user plane data, for example: a channel (i.e. a user plane transmission logic channel) is established with the terminal, and a data packet between the terminal and the DN is forwarded on the channel, so that the channel is responsible for filtering data messages of the terminal, forwarding 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, which is not limited.

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

In the embodiment of the present application, the network device is mainly used for implementing functions such as a physical layer function, resource scheduling and management, access control of the terminal device, and mobility management. The network device may be a device supporting wired access or a device supporting wireless access. Illustratively, the access network device may be AN Access Network (AN)/Radio Access Network (RAN), and may be composed of a plurality of 5G-AN/5G-RAN nodes. The 5G-AN/5G-RAN node may be: an Access Point (AP), a base station (nodeB, NB), an enhanced base station (eNB), a next generation base station (NR nodeB, gNB), a Transmission Reception Point (TRP), a Transmission Point (TP), or some other access node, etc.

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

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

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

Further, the communication device 400 may further 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 (CPU), a general purpose processor, a Network Processor (NP), a Digital Signal Processor (DSP), a microprocessor, a microcontroller, a Programmable Logic Device (PLD), or any combination thereof. The processor 401 may also be other means having processing functionality, such as, without limitation, a circuit, a device, or a software module.

A communication interface 402 for communicating with other devices or other communication networks. The other communication network may be an ethernet network, a wireless access network, a Wireless Local Area Network (WLAN), or the like. The communication interface 402 may be a module, circuitry, communication interface, or any device capable of enabling communication.

A communication line 403 for transmitting information between the respective components included in the communication apparatus 400.

A memory 404 for storing instructions. Wherein the instructions may be a computer program.

The memory 404 may be a read-only memory (ROM) or other types of static storage devices that can store static information and/or instructions, a Random Access Memory (RAM) or other types of dynamic storage devices that can store information and/or instructions, an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compact disc, laser disc, optical disc, digital versatile disc, blu-ray disc, etc.), a magnetic disc storage medium or other magnetic storage devices, and the like, without limitation.

It is noted that the memory 404 may exist independently of the processor 401 or may be integrated with the processor 401. The memory 404 may be used for storing instructions or program code or some data or the like. The memory 404 may be located within the communication device 400 or may be located outside the communication device 400, without limitation. A processor 401 configured to execute the instructions stored in the memory 404 to implement the method for determining the antenna parameter provided in the following embodiments 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 device 400 includes multiple 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 includes an output device 404 and an input device 406. Illustratively, the input device 406 is a keyboard, mouse, microphone, or joystick-like device, and the output device 404 is a display screen, speaker (microphone), or the like.

It is noted that the communication apparatus 400 may be a desktop computer, a portable computer, a network server, a mobile phone, a tablet computer, a wireless terminal, an embedded device, a chip system or a device with a similar structure as that in fig. 4. Further, the component structures shown in FIG. 4 are not intended to limit the various devices of FIG. 3, and in addition to the components shown in FIG. 4, the various devices of FIG. 3 may include more or less components than those shown, or some components may be combined, or a different arrangement of components may be used.

In the embodiment of the present application, the chip system may be formed by a chip, and may also include a chip and other discrete devices.

In addition, acts, terms, and the like referred to between the embodiments of the present application may be mutually referenced and are not limited. In the embodiment of the present application, the name of the message exchanged between the devices or the name of the parameter in the message, etc. are only an example, and other names may also be used in the specific implementation, which is not limited.

In the embodiments of the present application, terms such as "first" and "second" are used to distinguish the same or similar items having substantially the same function and action. For example, the first carrier determination policy and the second carrier determination policy are only used for distinguishing different carrier determination policies, and the order of the carrier determination policies is not limited. Those skilled in the art will appreciate that the terms "first," "second," etc. do not denote any order or quantity, nor do the terms "first," "second," etc. denote any order or importance.

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

In the present application, "at least one" means one or more, "a plurality" means two or more. "and/or" describes the association relationship of the associated objects, meaning that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone, wherein A and B can be singular or plural. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship. "at least one of the following" or similar expressions refer to any combination of these items, including any combination of the singular or plural items. 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 multiple.

The following describes a carrier determination method provided in an embodiment of the present application with reference to the communication system shown in fig. 1. In the following description, the terms and the like used in the embodiments of the present application are not limited to the specific embodiments described above. In the embodiment of the present application, the name of the message exchanged between the devices or the name of the parameter in the message, etc. are only an example, and other names may also be used in the specific implementation, which is not limited. The actions related to the embodiments of the present application are only an example, and other names may also be used in specific implementations, such as: the term "comprising" in the embodiments of the present application may also be replaced by "carrying" or "carrying" etc.

Fig. 5 provides a data transmission method for the embodiment of the present application, and as shown in fig. 5, the method includes:

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

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 a user of the target vehicle-mounted terminal is a user of the area where the target session management function network element is located and whether the DNN of the user is a dedicated DNN. The target MEC server and the target session management function network element are positioned in the same area. For example, in connection with the communication system shown in fig. 3, the target MEC server may be a second MEC server.

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

S502, when the user does not belong to the user of 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 the 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 the initial DNN parameter of the using user. The initial location may refer to a location where the user is registered. The parameters of the DNN may be used to determine whether the DNN is a private 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, the ID may be an Identity Document (ID). 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 network element may be the first user plane network element in 3. The MEC server may initially be the first MEC server in fig. 3.

For example, the initial user plane function network element may send the information of the roaming MEC server to the initial MEC server after receiving the first indication information. The initial 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 initial MEC server and the target MEC server may refer to the description of the subsequent embodiments, which are not described herein in detail.

It should be noted that, in the embodiment of the present application, the data synchronization between the initial MEC server and the target MEC server may include the synchronization of service data and the 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 for the target vehicle-mounted terminal. The user information may include identification information of the user, etc. 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 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 who does not belong 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 a user who does not belong to the area where the target session management function is located. And 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 user is a dedicated DNN according to the parameter of the DNN information. For example, when the parameter of the DNN using the user is a preset parameter, the DNN is a dedicated DNN. When the parameter of using the user's DNN 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 scheme 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 located area and the DNN of the user is the dedicated DNN, the initial UPF of the vehicle-mounted terminal may be accessed through the UPF (that is, the roaming place UPF) of the area to which the vehicle-mounted terminal belongs, and then data synchronization between the initial MEC server of the vehicle-mounted terminal and the roaming place MEC server is triggered. Therefore, the MEC server in the roaming place can continuously provide data service for the vehicle-mounted terminal after data synchronization, 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 used for requesting to process the first service data.

In one example, as shown in fig. 3, when the in-vehicle terminal roams from a first area to a second area, the in-vehicle terminal may transmit 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 functional network element is the user plane functional network element closest to the target vehicle-mounted terminal in the area where the target session management functional network element is located, and the second access request is used for requesting processing of 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 different user plane functional network elements, and are not limited. In fig. 6, the first target user plane function 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 functional network element may be a user plane functional network element closest to the vehicle terminal among the plurality of target user plane functional 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 initial MEC server, the target MEC server can process the first service data.

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

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

s701, the target MEC server receives a 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 open function network element. Accordingly, the network open function network element 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 initial MEC server. The changed transmission path is a transmission path between the target vehicle-mounted terminal and the target MEC server.

In one example, the target MEC server may accept subscriber information from a network open function network element. The user information may include information of users of an area where the target MEC server is located. For example, the user information may include one or more of a Type Allocation Code (TAC), an international mobile subscriber identity number (IMSI), a Data Network Access Identifier (DNAI), and a user permanent identifier (SUPI).

In a possible implementation manner, after the UPF initially receives the access request of the vehicle-mounted terminal, the subscription information may be sent to the network element with the network open function. The subscription information is used for subscribing the user information. After receiving the subscription information, the network element with the network open function may open a subscription function. The subscription function may be configured to send the user information to an MEC server of an access network open function network element. For example, the network open function network element may send 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 in-vehicle terminal is a user in the local 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 user information received by the target MEC server from the network open function network element, it indicates 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 configured with the user information of the located area in advance. And if the information of the 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 user information is consistent with the user information, the target vehicle-mounted terminal belongs to the user of the area where the target MEC server is located.

Further, the network element of the network open function may perform an 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 is successfully established, the transmission path between the initially 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 in-vehicle terminal, the target in-vehicle terminal may subsequently send a request for processing the service data to the target MEC server. The target MEC server can return the processing result of the service data to the target vehicle-mounted terminal.

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

In one possible embodiment, the method may further comprise:

and the target session management function network element receives the transmission path change information from the network open function network element.

Wherein the transmission path change information is used for instructing to change the transmission path between the target vehicle-mounted terminal and the initial MEC server to the transmission path between the target vehicle-mounted terminal and the target MEC server or instructing the changed transmission path.

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

Based on the embodiment, the target session management function network element may determine that the transmission path between the target vehicle-mounted terminal and the target MEC server is already 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 the initial MEC server of the target vehicle-mounted terminal.

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

S802, after the data synchronization between the target MEC server and the initial 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 the information indicating that the 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 initial MEC server. When the data synchronization time exceeds a preset time, it may be determined that the data synchronization is completed. After determining that the data synchronization with the initial 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 scheme of fig. 8, the target MEC server may obtain the service required by the target vehicle-mounted terminal through data synchronization with the initial MEC server. Further, the target MEC server can continue to provide the service of the service data to the target in-vehicle terminal.

The method provided in the embodiment of the present application is described below with reference to specific network elements.

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

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

Wherein the access request may be for requesting access to the initial MEC server. For example, the access request may be a DNS access request.

In one example, the target in-vehicle terminal may send an access request to a network device in the area where the target in-vehicle terminal is located. The network device, after receiving the access request, may forward to the initial SMF through the AMF.

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

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

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

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

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

The subscription message is used for subscribing the user information.

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

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

And S906, after the target vehicle-mounted terminal moves to the roaming place, the target vehicle-mounted terminal sends an inquiry request to the SMF of the roaming place at the roaming place.

The fact that the target vehicle-mounted terminal moves to the roaming place means that the target vehicle-mounted terminal moves from the area where the initial MEC server is located to the area where other MEC servers (namely, the MEC server at the roaming place) are located.

Wherein, the query request is used to query the identification information (such as Internet Protocol (IP) address information) of the MEC server at the roaming place.

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

The second UPF may be a UPF closest to the target vehicle-mounted terminal among a plurality of UPFs in the roaming area. The inquiry request includes DNN information of the user of the target vehicle-mounted terminal. The DNN information may carry/include location information and parameter information of the DNN. The location information may refer to location information of an initial location. The parameter information of the DNN is used to identify whether the DNN is a proprietary DNN (i.e., a business-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 in-vehicle 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 the initial UPF (i.e., the first UPF) corresponding to the visited target vehicle-mounted 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-destination MEC. For example, the second UPF may send an access request to the first UPF over the N9 interface.

In one example, the second UPF may start a network source address translation (SNAT) function after receiving a message from the roaming SMF to indicate an initial UPF corresponding to the visited target vehicle-mounted terminal. The SNAT function can refer to the prior art and is not described in detail.

In another example, when the query request in S906 further includes the 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 sends the service data to be processed or the identification information of the MEC server of the roaming place to the initial MEC server.

S910, the initial MEC server sends a message for requesting a data synchronization request to the roaming MEC server.

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

S911, the roaming-place MEC server performs data synchronization with the initial MEC server after receiving the message for requesting data synchronization from the initial MEC server.

In one example, the roaming-place MEC server may determine whether the data synchronization is completed according to a preset time threshold. For example, if the data synchronization process between the roaming MEC server and the initial MEC server exceeds the time threshold, it is determined that the data synchronization is completed.

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

S912, the target in-vehicle terminal sends an access request to the SMF of the roaming destination again.

Wherein the access request can be used to request processing of the first service data. The access information comprises information of a user of the target vehicle-mounted terminal and first service data.

And S913, the SMF at the roaming place determines a third UPF.

And 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 or different from the second UPF.

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

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

For example, the roaming-place MEC server may determine whether the user of the target in-vehicle terminal is a local 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 user is a non-local user. And under the condition that the using user is a non-local user, the first service data is non-local service data.

As another example, the roamed MEC server may identify the subscriber information from the NEF as both non-local subscribers. Therefore, when an access request is subsequently received, if the user information carried in the access request is consistent with the user information marked as the non-local user, the user information is determined as the non-local user.

And S916, the NEF changes the transmission path.

For example, the NEF may establish a transmission path between the target in-vehicle terminal and the roaming-location MEC server through the PCF, the roaming-location 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 MEC server of the roaming place through the SMF and the third UPF of the roaming place, 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 MEC server of the roaming place can be accessed by adopting a DNN customization mode, so that the service continuity is ensured, and the requirement of the low-delay service of the target vehicle-mounted terminal is met.

All the schemes in the above embodiments of the present application can be combined without contradiction.

In the embodiment of the present application, the communication apparatus may be divided into functional modules or functional units according to the method example, for example, each functional module or functional unit may be divided according to each function, or two or more functions may be integrated into one processing module. The integrated module may be implemented in a form of hardware, or may be implemented in a form of a software functional module or a functional unit. The division of the modules or units in the embodiment of the present application is schematic, and is only a logic function division, and there may be another division manner in actual implementation.

In the case of dividing each functional module according to each function, fig. 10 is a schematic structural diagram of a communication device 100, where the communication device 100 may be a target session management function network element, and may also be a chip applied to the target session management function network element, and the communication device 100 may be configured to execute the function of the target session management function network element in the foregoing embodiment. 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 in-vehicle 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, and the first access request includes DNN information of a user using the target in-vehicle terminal, and 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 1002, configured to send, to a first target user plane function network element, first instruction information when a 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, 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 a target MEC server, and the information of the target MEC is used for data synchronization between the initial MEC server of the target vehicle-mounted terminal and the target MEC server.

In a possible implementation manner, the apparatus further includes a determining unit; a receiving unit 1001, configured to receive a second access request from a target in-vehicle terminal, where the second access request includes information of the user; and the determining unit is used for 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 the user plane function network element which is 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.

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

In one possible design, the communication device 100 shown in fig. 10 may further include a storage unit 1003. The memory 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 functionality of the communication unit 1001. The transmitting unit 1002 in fig. 10 may be replaced by a transceiver or transceiving unit, which may integrate the functionality of the communication unit 1002.

Further, when the receiving unit 1001 is replaced by a transceiver or a transmitting/receiving unit and the transmitting unit 1002 is replaced by a transceiver or a transmitting/receiving 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 each functional module according to each function, fig. 11 shows a schematic structural diagram of a communication device 110, where 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 configured to execute the function of the target MEC server in the foregoing 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 in-vehicle terminal;

a sending unit 1102, configured to send first request information to a network element of a network open function if a user of the target vehicle-mounted terminal is not a user in an area where the target MEC server is located, where the first request information is used to request a change of 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 a target vehicle-mounted terminal, where the data synchronization request is used to request data synchronization with the target MEC server; the sending unit 1102 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 functional network element, where the first target user plane functional network element is a user plane functional network element determined when the target session management functional network element first receives an access request of a target vehicle, and the target session management functional network element and the target MEC server are in the same area.

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

the information of the use 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.

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

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

Further, when the receiving unit 1101 is replaced by a transceiver or a transceiver unit, and the transmitting unit 1102 is replaced by a transceiver or a transceiver 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 processes in the above method embodiments may be performed by relevant hardware instructed by a computer program, which may be stored in the above computer-readable storage medium, and when executed, may include the processes in the above method embodiments. The computer readable storage medium may be an internal storage unit of the communication device (including the data sending end and/or the data receiving end) of any previous embodiment, such as a hard disk or a memory of the communication device. The computer readable storage medium may also be an external storage device of the terminal device, such as a plug-in hard disk, a Smart Memory Card (SMC), a Secure Digital (SD) card, a flash memory card (flash card), and the like, which are provided on the terminal device. Further, the computer-readable storage medium may include both an internal storage unit and an external storage device of the communication apparatus. The computer-readable storage medium stores the computer program and other programs and data required by the communication apparatus. 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, claims and drawings of the present application are used for distinguishing different objects and not for describing a particular order. Furthermore, the terms "include" and "have," as well as any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those steps or elements but may alternatively include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

It should be understood that in the present application, "at least one" means one or more, "a plurality" means two or more, "at least two" means two or three and three or more, "and/or" for describing an association relationship of associated objects, meaning that three relationships may exist, for example, "a and/or B" may mean: only A, only B and both A and B are present, wherein A and B may be singular or plural. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship. "at least one of the following" or similar expressions refer to any combination of these items, including any combination of single item(s) or plural items. 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 and c may be single or plural.

Through the above description of the embodiments, it is clear to those skilled in the art that, for convenience and simplicity of description, the foregoing division of the functional modules is merely used as an example, and in practical applications, the above function distribution may be completed by different functional modules according to needs, that is, the internal structure of the device may be divided into different functional modules to complete all or part of the above described functions.

In the several embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other manners. For example, the above-described device embodiments are merely illustrative, and for example, the division of the modules or units is only one type of logical functional division, and other divisions may be realized in practice, for example, multiple units or components may be combined or integrated into another device, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

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

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit size may exist alone physically, or two or more units may be integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a readable storage medium. Based on such understanding, the technical solutions of the embodiments of the present application may be essentially or partially contributed to by the prior art, or all or part of the technical solutions may be embodied in the form of a software product, where the software product is stored in a storage medium and includes several instructions to enable a device (which may be a single chip, a chip, or the like) or a processor (processor) to execute all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a U disk, a removable hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.

The above description is only an embodiment of the present application, but the scope of the present application is not limited thereto, and any changes or substitutions within the technical scope disclosed in the present application should be covered within the scope of the present application. Therefore, the protection scope of the present application shall be 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 the target session management function network element is located, the first access request comprises data network identification (DNN) information of a user using 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 the DNN of the user is a private DNN;

and sending first indication information to a first target user plane function network element when 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 dedicated DNN, 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, and the information of the target MEC is used for data synchronization between the initial MEC server of the target vehicle-mounted terminal and the target MEC server.

2. The method of claim 1, further comprising:

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

and 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, where 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 first service data.

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

receiving transmission path change information from a network element with a 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.

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

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

and 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 open function network element, 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 of claim 4, further comprising:

receiving a data synchronization request of an initial MEC server from the target vehicle-mounted terminal, wherein the data synchronization request is used for requesting data synchronization with the target MEC server;

after the data synchronization with the initial MEC server is completed, sending information indicating the completion of the data synchronization 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 open function network element, 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 the user of the area where the target MEC server is located, and the method comprises the following steps:

and the information of the user using 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 communications apparatus, adapted for use in a target session management function network element, the apparatus 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, and the information of the target MEC is used for data synchronization between the initial MEC server of the target vehicle-mounted terminal and the target MEC server.

8. The apparatus according to claim 7, wherein the apparatus further comprises a determining 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 the second access request to the target MEC server 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 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 to request processing of 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 of an openwork network, the transmission path change information being used to instruct to change the transmission path between the target vehicle-mounted terminal and the initial MEC server to the transmission path between the target vehicle-mounted terminal and the target MEC server.

10. A communication apparatus, applied to a target MEC server, the apparatus comprising:

a sending unit, configured to send, if a user of the target vehicle-mounted terminal is not a user of an area where the target MEC server is located, first request information to a network open function network element, where the first request information is used to request a change of a 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 receiving unit is further configured to receive a data synchronization request from an initial MEC server of the target vehicle-mounted terminal, the data synchronization request requesting data synchronization with the target MEC server;

the sending unit is further configured to send information indicating that data synchronization is completed to a first target user plane function network element after the data synchronization with the initial MEC server is completed, 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 for the first time, and the target session management function network element and the target MEC server are in the same area.

12. The apparatus according to claim 10 or 11, wherein the receiving unit is further configured to receive user information from the network element, 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 stored therein instructions that, when executed, implement the method of any one of claims 1-3 or any one of claims 4-6.

14. A communications apparatus, comprising: a processor, a memory, and a communication interface; wherein, the communication interface is used for the communication device to communicate with other equipment or networks; the memory is used for storing one or more programs, the one or more programs including computer executable instructions, which when executed by the communication device, are executed by the processor to cause the communication device to perform the method of any of claims 1-3 or any of claims 4-6.